mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	"masahiroy@kernel.org" <masahiroy@kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] powerpc/vdso: augment VDSO32 functions to support 64 bits build
Date: Wed, 22 Dec 2021 07:36:29 +0000	[thread overview]
Message-ID: <71edc2a9-2547-7443-e899-a1696bda22c1@csgroup.eu> (raw)
In-Reply-To: <20211221193608.GD614@gate.crashing.org>



Le 21/12/2021 à 20:36, Segher Boessenkool a écrit :
> On Tue, Dec 21, 2021 at 05:49:33PM +0000, Christophe Leroy wrote:
>> diff --git a/arch/powerpc/kernel/vdso32/datapage.S b/arch/powerpc/kernel/vdso32/datapage.S
>> index 65244416ab94..db8e167f0166 100644
>> --- a/arch/powerpc/kernel/vdso32/datapage.S
>> +++ b/arch/powerpc/kernel/vdso32/datapage.S
>> @@ -30,11 +30,15 @@ V_FUNCTION_BEGIN(__kernel_get_syscall_map)
>>   	mr.	r4,r3
>>   	get_datapage	r3
>>   	mtlr	r12
>> +#ifdef __powerpc64__
>> +	addi	r3,r3,CFG_SYSCALL_MAP64
>> +#else
>>   	addi	r3,r3,CFG_SYSCALL_MAP32
>> +#endif
>> +	crclr	cr0*4+so
>>   	beqlr
>>   	li	r0,NR_syscalls
>>   	stw	r0,0(r4)
>> -	crclr	cr0*4+so
>>   	blr
> 
> This now clears cr0.3 if r3 is zero on entry.  Is that on purpose?

All crclr where added by commit 5d66da3d71e6 ("[PATCH] powerpc: Make the 
vDSO functions set error code (#2)")

It looks like it was properly added to ppc64's version of 
__kernel_get_syscall_map() but for ppc32 CR.SO was left undefined in 
case of early exit of __kernel_get_syscall_map()

So yes, I think the change is on purpose.

> 
> Rest looks good.
> 
> Reviewed-by: Segher Boessenkool <segher@kernel.crashing.org>
> 

Thanks
Christophe

      reply	other threads:[~2021-12-22  7:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 17:49 Christophe Leroy
2021-12-21 17:49 ` [PATCH 2/3] powerpc/vdso: Rework VDSO32 makefile to add a prefix to object files Christophe Leroy
2021-12-21 17:49 ` [PATCH 3/3] powerpc/vdso: Merge vdso64 and vdso32 into a single directory Christophe Leroy
2021-12-22  9:25   ` kernel test robot
2021-12-22  9:50     ` Christophe Leroy
2021-12-21 19:36 ` [PATCH 1/3] powerpc/vdso: augment VDSO32 functions to support 64 bits build Segher Boessenkool
2021-12-22  7:36   ` Christophe Leroy [this message]

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=71edc2a9-2547-7443-e899-a1696bda22c1@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=masahiroy@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.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®