On 05/28/2015 03:35 PM, Ross Zwisler wrote:
> Add a new PMEM API to x86, and allow for architectures that do not
> implement this API. Architectures that implement the PMEM API should
> define ARCH_HAS_PMEM_API in their kernel configuration and must provide
> implementations for persistent_copy(), persistent_flush() and
> persistent_sync().
>
> void clflush_cache_range(void *addr, unsigned int size);
>
No, no, no, no, no. Include the proper header file.
> +static inline void arch_persistent_flush(void *vaddr, size_t size)
> +{
> + clflush_cache_range(vaddr, size);
> +}
Shouldn't this really be using clwb() -- we really need a
clwb_cache_range() I guess?
Incidentally, clflush_cache_range() seems to have the same flaw as the
proposed use case for clwb() had... if the buffer is aligned it will
needlessly flush the last line twice. It should really look something
like this (which would be a good standalone patch):
void clflush_cache_range(void *vaddr, unsigned int size)
{
void *vend = vaddr + size - 1;
mb();
vaddr = (void *)
((unsigned long)vaddr
& ~(boot_cpu_data.x86_clflush_size - 1));
for (; vaddr < vend; vaddr += boot_cpu_data.x86_clflush_size)
clflushopt(vaddr);
mb();
}
EXPORT_SYMBOL_GPL(clflush_cache_range);
I also note that with your implementation we have a wmb() in
arch_persistent_sync() and an mb() in arch_persistent_flush()... surely
one is redundant?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
