From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, npiggin@gmail.com,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/uaccess: Implement unsafe_put_user() using 'asm goto'
Date: Thu, 16 Apr 2020 14:41:56 +0200 [thread overview]
Message-ID: <f797e5ac-a29a-0eb0-89c8-ff0a9f537ccf@c-s.fr> (raw)
In-Reply-To: <20200415223747.GX26902@gate.crashing.org>
Le 16/04/2020 à 00:37, Segher Boessenkool a écrit :
> Hi!
>
> On Wed, Apr 15, 2020 at 09:25:59AM +0000, Christophe Leroy wrote:
>> +#define __put_user_goto(x, ptr, label) \
>> + __put_user_nocheck_goto((__typeof__(*(ptr)))(x), (ptr), sizeof(*(ptr)), label)
>
> This line gets too long, can you break it up somehow?
This line has 86 chars.
powerpc arch tolerates lines with up to 90 chars, see
arch/powerpc/tools/checkpatch.sh
>
>> +#define __put_user_asm_goto(x, addr, label, op) \
>> + asm volatile goto( \
>> + "1: " op "%U1%X1 %0,%1 # put_user\n" \
>> + EX_TABLE(1b, %l2) \
>> + : \
>> + : "r" (x), "m" (*addr) \
>> + : \
>> + : label)
>
> Same "%Un" problem as in the other patch. You could use "m<>" here,
> but maybe just dropping "%Un" is better.
Ok.
I kept it to be consistent with the other patch.
>
>> +#ifdef __powerpc64__
>> +#define __put_user_asm2_goto(x, ptr, label) \
>> + __put_user_asm_goto(x, ptr, label, "std")
>> +#else /* __powerpc64__ */
>> +#define __put_user_asm2_goto(x, addr, label) \
>> + asm volatile goto( \
>> + "1: stw%U1%X1 %0, %1\n" \
>> + "2: stw%U1%X1 %L0, %L1\n" \
>> + EX_TABLE(1b, %l2) \
>> + EX_TABLE(2b, %l2) \
>> + : \
>> + : "r" (x), "m" (*addr) \
>> + : \
>> + : label)
>> +#endif /* __powerpc64__ */
>
> Here, you should drop it for sure.
Done.
Christophe
next prev parent reply other threads:[~2020-04-16 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 9:25 [PATCH v2] powerpc/uaccess: Implement unsafe_put_user() using 'asm goto' Christophe Leroy
2020-04-15 22:37 ` Segher Boessenkool
2020-04-16 12:41 ` Christophe Leroy [this message]
2020-04-16 19:01 ` Segher Boessenkool
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=f797e5ac-a29a-0eb0-89c8-ff0a9f537ccf@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).