From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH -tip 0/4] x86: signal handler improvement
Date: Tue, 23 Sep 2008 10:00:56 -0700 [thread overview]
Message-ID: <48D920C8.2060600@ct.jp.nec.com> (raw)
In-Reply-To: <20080923085518.GA29703@elte.hu>
Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> could we perhaps first finish unifying them into signal.c, and then
>> introduce __put_user_cerr() in signal_32/64.c?
>
> i've got an API suggestion as well. Instead of:
>
> - err |= __put_user(UC_FP_XSTATE, &frame->uc.uc_flags);
> + __put_user_cerr(UC_FP_XSTATE, &frame->uc.uc_flags, err);
>
> could you instead please make it:
>
> + __put_user_cerr(UC_FP_XSTATE, &frame->uc.uc_flags, &err);
>
> i.e. pass in 'err' as a reference. This makes it clear to the casual
> reader, in a C calling convention sense, that there's a side-effect to
> 'err'. [ There should be no change to the resulting code as
> __put_user_cerr() is a macro. ]
make sense!
Will do in next post.
thanks,
Hiroshi Shimamoto
next prev parent reply other threads:[~2008-09-23 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 1:45 [RFC PATCH -tip 0/4] x86: signal handler improvement Hiroshi Shimamoto
2008-09-23 1:50 ` [RFC PATCH -tip 1/4] x86: uaccess: rename __put_user_u64 to __put_user_asm_u64 Hiroshi Shimamoto
2008-09-23 1:51 ` [RFC PATCH -tip 2/4] x86: uaccess: introduce __{put|get}_user_asm_eop Hiroshi Shimamoto
2008-09-23 1:51 ` [RFC PATCH -tip 3/4] x86: uaccess: introduce __{put|get}_user_cerr Hiroshi Shimamoto
2008-09-23 1:51 ` [RFC PATCH -tip 4/4] x86: signal: use __{put|get}_user_cerr Hiroshi Shimamoto
2008-09-23 8:50 ` [RFC PATCH -tip 0/4] x86: signal handler improvement Ingo Molnar
2008-09-23 8:55 ` Ingo Molnar
2008-09-23 17:00 ` Hiroshi Shimamoto [this message]
2008-09-23 16:58 ` Hiroshi Shimamoto
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=48D920C8.2060600@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.