From: Pranith Kumar <bobby.prani@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@iki.fi>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
Allan Wirth <awirth@akamai.com>,
Laurent Vivier <lvivier@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] linux-user: Add signal handling for x86_64
Date: Fri, 03 Feb 2017 10:55:42 -0500 [thread overview]
Message-ID: <87y3xnp8u9.fsf@gmail.com> (raw)
In-Reply-To: <CAFEAcA-pdY6J_e035PGj5nxYrtN7V0SJMxMuaE0VECNJVKg5iQ@mail.gmail.com>
Peter Maydell writes:
> On 25 January 2017 at 00:10, Pranith Kumar <bobby.prani@gmail.com> wrote:
>> Adopted from a previous patch posting:
>> https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg02079.html
>>
>> CC: Allan Wirth <awirth@akamai.com>
>> CC: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
>
> Thanks for picking this patch up. A nit about commit message format:
> because this is mostly Allan's work you need to add his signed-off-by:
> line (which he provided on his original patch posting), and make
> a brief not of what was changed, so it looks like:
>
> Signed-off-by: Original Author <oa@example.com>
> [OP: changed X, Y, Z]
> Signed-off-by: Other Person <other@person.org>
>
> It's also in this kind of situation worth considering whether the
> patch would be better attributed to Allan as the git commit 'author'.
> If I've taken somebody else's work and made mostly minor overhauls
> to it I tend to go for giving them credit in the git commit log.
OK, I'll add these SOB lines and attribute it to Allan as he did most of the work.
>
>> ---
>> linux-user/signal.c | 264 ++++++++++++++++++++++++++++++++++++++++-------
>> target/i386/cpu.h | 2 +
>> target/i386/fpu_helper.c | 12 +++
>> 3 files changed, 242 insertions(+), 36 deletions(-)
>>
>> diff --git a/linux-user/signal.c b/linux-user/signal.c
>> index 0a5bb4e26b..0248621d66 100644
>> --- a/linux-user/signal.c
>> +++ b/linux-user/signal.c
>> @@ -253,8 +253,7 @@ int do_sigprocmask(int how, const sigset_t *set, sigset_t *oldset)
>> return 0;
>> }
>>
>> -#if !defined(TARGET_OPENRISC) && !defined(TARGET_UNICORE32) && \
>> - !defined(TARGET_X86_64)
>> +#if !defined(TARGET_OPENRISC) && !defined(TARGET_UNICORE32)
>> /* Just set the guest's signal mask to the specified value; the
>> * caller is assumed to have called block_signals() already.
>> */
>
> There's a minor conflict here with the Nios2 code that's now
> in master (which added another clause to this #if), but it's
> trivial to resolve.
I'll rebase my patch on master and fix up the conflicts and send a v2.
>
> Otherwise:
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Thanks for the review!
--
Pranith
next prev parent reply other threads:[~2017-02-03 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 0:10 [Qemu-devel] [RFC PATCH] linux-user: Add signal handling for x86_64 Pranith Kumar
2017-02-03 13:12 ` Peter Maydell
2017-02-03 15:55 ` Pranith Kumar [this message]
2017-02-03 16:10 ` Wirth, Allan
2017-02-03 20:39 ` Pranith Kumar
2017-02-03 21:56 ` Laurent Vivier
2017-02-06 7:04 ` Pranith Kumar
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=87y3xnp8u9.fsf@gmail.com \
--to=bobby.prani@gmail.com \
--cc=awirth@akamai.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
/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.