linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Julian Vetter <julian@outer-limits.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Naveen N Rao <naveen@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Remove eieio in _memcpy_fromio
Date: Tue, 28 Jan 2025 16:24:07 +0100	[thread overview]
Message-ID: <e785c98f-4bf9-48ab-a102-dc531623b378@csgroup.eu> (raw)
In-Reply-To: <b335d035-07a4-457d-99ea-8b7597782fd9@outer-limits.org>



Le 28/01/2025 à 16:07, Julian Vetter a écrit :
> [Vous ne recevez pas souvent de courriers de julian@outer-limits.org. 
> Découvrez pourquoi ceci est important à https://aka.ms/ 
> LearnAboutSenderIdentification ]
> 
> On 1/28/25 15:16, Christophe Leroy wrote:
>>
>>
>> Le 28/01/2025 à 14:57, Julian Vetter a écrit :
>>> Remove the eieio() calls in _memcpy_fromio, to bring its implementation
>>> closer to the one from lib/iomem_copy.c. These eieio() calls don't seem
>>> to be necessary, because the _memcpy_toio completely omits them. Also
>>> the legacy code from ppc was not doing them.
>>
>> What do you mean exactly by "legacy code" ?
>>
>> As far as I can see they were already there before commit 68a64357d15a
>> ("[POWERPC] Merge 32 and 64 bits asm-powerpc/io.h"):
>>
> 
> With 'ppc' I was refering to 'include/asm-ppc/io.h'. But you're right,
> when going back a bit, in the 'include/asm-powerpc/io.h' there are two
> cases, one (eeh_memcpy_fromio) which does the the 'eieio', and a second,
> i.e., 'iSeries_memcpy_fromio' which does a byte-wise copy. But in the
> ppc code ('include/asm-ppc/io.h') there is a simple memcpy. I was
> referring to this one. But my description is not very clear. Sorry for 
> that.

But then is your change still valid ? Isn't there some corner case that 
still need it ? Is it a valid argument that because memcpy_toio() 
doesn't need it memcpy_fromio() doesn't need it either ?

> 
>> -static inline void eeh_memcpy_fromio(void *dest, const volatile void
>> __iomem *src,
>> +static inline void eeh_memcpy_fromio(void *dest, const
>> +                     volatile void __iomem *src,
>>                        unsigned long n)
>>   {
>> -    void *vsrc = (void __force *) src;
>> -    void *destsave = dest;
>> -    unsigned long nsave = n;
>> -
>> -    __asm__ __volatile__ ("sync" : : : "memory");
>> -    while(n && (!EEH_CHECK_ALIGN(vsrc, 4) || !EEH_CHECK_ALIGN(dest, 
>> 4))) {
>> -        *((u8 *)dest) = *((volatile u8 *)vsrc);
>> -        __asm__ __volatile__ ("eieio" : : : "memory");
>> -        vsrc++;
>> -        dest++;
>> -        n--;
>> -    }
>> -    while(n > 4) {
>> -        *((u32 *)dest) = *((volatile u32 *)vsrc);
>> -        __asm__ __volatile__ ("eieio" : : : "memory");
>> -        vsrc += 4;
>> -        dest += 4;
>> -        n -= 4;
>> -    }
>> -    while(n) {
>> -        *((u8 *)dest) = *((volatile u8 *)vsrc);
>> -        __asm__ __volatile__ ("eieio" : : : "memory");
>> -        vsrc++;
>> -        dest++;
>> -        n--;
>> -    }
>> -    __asm__ __volatile__ ("sync" : : : "memory");
>> +    _memcpy_fromio(dest, src, n);
>>
>>       /* Look for ffff's here at dest[n].  Assume that at least 4 bytes
>>        * were copied. Check all four bytes.
>>        */
>> -    if ((nsave >= 4) &&
>> -        (EEH_POSSIBLE_ERROR((*((u32 *) destsave+nsave-4)), u32))) {
>> -        eeh_check_failure(src, (*((u32 *) destsave+nsave-4)));
>> -    }
>> +    if (n >= 4 && EEH_POSSIBLE_ERROR(*((u32 *)(dest + n - 4)), u32))
>> +        eeh_check_failure(src, *((u32 *)(dest + n - 4)));
>>   }
>>
>>
>>
>>>
>>> Signed-off-by: Julian Vetter <julian@outer-limits.org>
>>> ---
>>>   arch/powerpc/kernel/io.c | 3 ---
>>>   1 file changed, 3 deletions(-)
>>>
>>> diff --git a/arch/powerpc/kernel/io.c b/arch/powerpc/kernel/io.c
>>> index 6af535905984..81e5d54260a1 100644
>>> --- a/arch/powerpc/kernel/io.c
>>> +++ b/arch/powerpc/kernel/io.c
>>> @@ -155,21 +155,18 @@ void _memcpy_fromio(void *dest, const volatile
>>> void __iomem *src,
>>>          __asm__ __volatile__ ("sync" : : : "memory");
>>>          while(n && (!IO_CHECK_ALIGN(vsrc, 4) || !IO_CHECK_ALIGN(dest,
>>> 4))) {
>>>                  *((u8 *)dest) = *((volatile u8 *)vsrc);
>>> -               eieio();
>>>                  vsrc++;
>>>                  dest++;
>>>                  n--;
>>>          }
>>>          while(n >= 4) {
>>>                  *((u32 *)dest) = *((volatile u32 *)vsrc);
>>> -               eieio();
>>>                  vsrc += 4;
>>>                  dest += 4;
>>>                  n -= 4;
>>>          }
>>>          while(n) {
>>>                  *((u8 *)dest) = *((volatile u8 *)vsrc);
>>> -               eieio();
>>>                  vsrc++;
>>>                  dest++;
>>>                  n--;
>>> -- 
>>> 2.34.1
>>>
>>



  reply	other threads:[~2025-01-28 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 13:57 [PATCH] powerpc: Remove eieio in _memcpy_fromio Julian Vetter
2025-01-28 14:16 ` Christophe Leroy
2025-01-28 15:07   ` Julian Vetter
2025-01-28 15:24     ` Christophe Leroy [this message]
2025-01-28 15:34       ` Christophe Leroy
2025-01-28 16:50         ` Arnd Bergmann

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=e785c98f-4bf9-48ab-a102-dc531623b378@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=arnd@arndb.de \
    --cc=julian@outer-limits.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).