LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nikhil Kumar Singh <nikhilks@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/64s: Clarify copy_and_flush() cache sync loop comment
Date: Tue, 7 Jul 2026 13:02:30 +0530	[thread overview]
Message-ID: <181d1951-b5f9-4057-92d9-57184a0b03b9@linux.ibm.com> (raw)
In-Reply-To: <akypcnslC8r_XG6D@li-1a3e774c-28e4-11b2-a85c-acc9f2883e29.ibm.com>

Hi Mukesh,

Thanks for the clarification, sorry I missed that part. I'll update the 
comment to follow the 80-column limit and keep the alignment consistent 
in the next revision.

Thanks,
~ Nikhil

On 07/07/26 12:54, Mukesh Kumar Chaurasiya wrote:
> On Tue, Jul 07, 2026 at 12:48:57PM +0530, Nikhil Kumar Singh wrote:
>> Hi Mukesh,
>>
>> Thanks for reviewing the patch and for the suggestion.
>> I'd prefer to keep the current alignment as I find it a bit more readable.
>>
>> Thanks,
>> ~ Nikhil
>>
> There is a reason we keep the character limit to 80 chars. Please go
> through these coding guidelines.
>
> https://docs.kernel.org/process/coding-style.html
>
> Regards,
> Mukesh
>
>> On 07/07/26 11:08, Mukesh Kumar Chaurasiya wrote:
>>> On Mon, Jul 06, 2026 at 01:57:08PM +0530, Nikhil Kumar Singh wrote:
>>>> The value loaded into r0 in copy_and_flush() represents the number of
>>>> 8-byte words processed between cache synchronization operations.
>>>>
>>>> The existing comment refers to cache line size, which can make it appear
>>>> that the value is a cache line size in bytes rather than a loop count.
>>>> Clarify the comment to explain that the loop processes 8 words (64 bytes)
>>>> per cache synchronization iteration, and that increasing the value would
>>>> skip cache maintenance for intermediate cache lines.
>>>>
>>>> This is a comment-only change with no functional impact.
>>>>
>>>> Signed-off-by: Nikhil Kumar Singh <nikhilks@linux.ibm.com>
>>>> ---
>>>>    arch/powerpc/kernel/head_64.S | 20 ++++++++++++--------
>>>>    1 file changed, 12 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
>>>> index 63432a33ec49..a54f6f979173 100644
>>>> --- a/arch/powerpc/kernel/head_64.S
>>>> +++ b/arch/powerpc/kernel/head_64.S
>>>> @@ -713,14 +713,18 @@ p_end: .8byte _end - copy_to_here
>>>>    _GLOBAL(copy_and_flush)
>>>>    	addi	r5,r5,-8
>>>>    	addi	r6,r6,-8
>>>> -4:	li	r0,8			/* Use the smallest common	*/
>>>> -					/* denominator cache line	*/
>>>> -					/* size.  This results in	*/
>>>> -					/* extra cache line flushes	*/
>>>> -					/* but operation is correct.	*/
>>>> -					/* Can't get cache line size	*/
>>>> -					/* from NACA as it is being	*/
>>>> -					/* moved too.			*/
>>>> +4:	li	r0,8			/* r0 is the number of 8-byte words	*/
>>>> +					/* to copy per cache sync iteration.	*/
>>>> +					/* 8 words * 8 bytes = 64 bytes. 64B is	*/
>>>> +					/* the current default cache line size.	*/
>>>> +					/* This is a loop count, not a byte	*/
>>>> +					/* count. Increasing it may skip	*/
>>>> +					/* dcbst/icbi for lines in between and	*/
>>>> +					/* leave stale instructions in icache.	*/
>>>> +					/* This results in extra cache line	*/
>>>> +					/* flushes but operation is correct.	*/
>>>> +					/* Can't get cache line size from NACA	*/
>>>> +					/* as it is being moved too.		*/
>>> The comment looks fine. But the alignement of the comment is still
>>> different from earlier. Keep the alignment same as earlier, it looks a
>>> little nicer.
>>>
>>> Regards,
>>> Mukesh
>>>>    	mtctr	r0			/* put # words/line in ctr	*/
>>>>    3:	addi	r6,r6,8			/* copy a cache line		*/
>>>> -- 
>>>> 2.43.5
>>>>


  reply	other threads:[~2026-07-07  7:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 18:27 [PATCH] powerpc/64s: Clarify copy_and_flush() cache sync loop comment Nikhil Kumar Singh
2026-07-01 18:38 ` Aditya Gupta
2026-07-02  5:28 ` Mukesh Kumar Chaurasiya
2026-07-06  8:27 ` [PATCH v2] " Nikhil Kumar Singh
2026-07-07  5:38   ` Mukesh Kumar Chaurasiya
2026-07-07  7:18     ` Nikhil Kumar Singh
2026-07-07  7:24       ` Mukesh Kumar Chaurasiya
2026-07-07  7:32         ` Nikhil Kumar Singh [this message]
2026-07-09  6:10       ` Nikhil Kumar Singh
2026-07-09  8:32         ` Mukesh Kumar Chaurasiya
2026-07-17 11:55         ` Amit Machhiwal
2026-07-17  6:40   ` Aditya Gupta
2026-07-17 14:52   ` Mahesh J Salgaonkar
2026-07-14 10:30 ` [PATCH] " Mahesh J Salgaonkar

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=181d1951-b5f9-4057-92d9-57184a0b03b9@linux.ibm.com \
    --to=nikhilks@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.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