From: hpa@zytor.com
To: Borislav Petkov <bp@suse.de>,
Logan Gunthorpe <logang@deltatee.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Tony Luck <tony.luck@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question Regarding ERMS memcpy
Date: Mon, 06 Mar 2017 05:41:22 -0800 [thread overview]
Message-ID: <86022C23-30AA-4501-ABEE-1154CB4FF61D@zytor.com> (raw)
In-Reply-To: <20170306133327.usksddtpum7fftqs@pd.tnic>
On March 6, 2017 5:33:28 AM PST, Borislav Petkov <bp@suse.de> wrote:
>On Mon, Mar 06, 2017 at 12:01:10AM -0700, Logan Gunthorpe wrote:
>> Well honestly my issue was solved by fixing my kernel config. I have
>no
>> idea why I had optimize for size in there in the first place.
>
>I still think that we should address the iomem memcpy Linus mentioned.
>So how about this partial revert. I've made 32-bit use the same special
>__memcpy() version.
>
>Hmmm?
>
>---
>diff --git a/arch/x86/include/asm/io.h b/arch/x86/include/asm/io.h
>index 7afb0e2f07f4..9e378a10796d 100644
>--- a/arch/x86/include/asm/io.h
>+++ b/arch/x86/include/asm/io.h
>@@ -201,6 +201,7 @@ extern void set_iounmap_nonlazy(void);
> #ifdef __KERNEL__
>
> #include <asm-generic/iomap.h>
>+#include <asm/string.h>
>
> /*
> * Convert a virtual cached pointer to an uncached pointer
>@@ -227,12 +228,13 @@ memset_io(volatile void __iomem *addr, unsigned
>char val, size_t count)
> * @src: The (I/O memory) source for the data
> * @count: The number of bytes to copy
> *
>- * Copy a block of data from I/O memory.
>+ * Copy a block of data from I/O memory. IO memory is different from
>+ * cached memory so we use special memcpy version.
> */
> static inline void
>memcpy_fromio(void *dst, const volatile void __iomem *src, size_t
>count)
> {
>- memcpy(dst, (const void __force *)src, count);
>+ __inline_memcpy(dst, (const void __force *)src, count);
> }
>
> /**
>@@ -241,12 +243,13 @@ memcpy_fromio(void *dst, const volatile void
>__iomem *src, size_t count)
> * @src: The (RAM) source for the data
> * @count: The number of bytes to copy
> *
>- * Copy a block of data to I/O memory.
>+ * Copy a block of data to I/O memory. IO memory is different from
>+ * cached memory so we use special memcpy version.
> */
> static inline void
> memcpy_toio(volatile void __iomem *dst, const void *src, size_t count)
> {
>- memcpy((void __force *)dst, src, count);
>+ __inline_memcpy((void __force *)dst, src, count);
> }
>
> /*
>diff --git a/arch/x86/include/asm/string_32.h
>b/arch/x86/include/asm/string_32.h
>index 3d3e8353ee5c..556fa4a975ff 100644
>--- a/arch/x86/include/asm/string_32.h
>+++ b/arch/x86/include/asm/string_32.h
>@@ -29,6 +29,7 @@ extern char *strchr(const char *s, int c);
> #define __HAVE_ARCH_STRLEN
> extern size_t strlen(const char *s);
>
>+#define __inline_memcpy __memcpy
>static __always_inline void *__memcpy(void *to, const void *from,
>size_t n)
> {
> int d0, d1, d2;
It isn't really that straightforward IMO.
For UC memory transaction size really needs to be specified explicitly at all times and should be part of the API, rather than implicit.
For WC/WT/WB device memory, the ordinary memcpy is valid and preferred.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2017-03-06 13:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 20:08 Logan Gunthorpe
2017-03-04 22:43 ` Borislav Petkov
[not found] ` <c675a6c8-e87a-ece2-2350-cdd079b1b610@deltatee.com>
2017-03-04 23:55 ` hpa
2017-03-05 0:14 ` Borislav Petkov
2017-03-05 0:23 ` hpa
2017-03-05 0:33 ` Borislav Petkov
2017-03-05 0:56 ` hpa
2017-03-05 9:50 ` Borislav Petkov
2017-03-05 11:18 ` Borislav Petkov
2017-03-05 13:05 ` Borislav Petkov
2017-03-05 19:19 ` Linus Torvalds
2017-03-05 19:54 ` Borislav Petkov
2017-03-05 20:19 ` Linus Torvalds
2017-03-06 7:01 ` Logan Gunthorpe
2017-03-06 7:28 ` H. Peter Anvin
2017-03-06 17:12 ` Logan Gunthorpe
2017-03-06 18:53 ` hpa
2017-03-06 13:33 ` Borislav Petkov
2017-03-06 13:41 ` hpa [this message]
2017-03-06 14:00 ` Borislav Petkov
2017-03-05 4:58 ` Logan Gunthorpe
2017-03-05 9:54 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86022C23-30AA-4501-ABEE-1154CB4FF61D@zytor.com \
--to=hpa@zytor.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®