From: Avi Kivity <avi@redhat.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [POC] mce: replace TIF_MCE_NOTIFY with TIF_USER_RETURN_NOTIFY
Date: Sun, 05 Jun 2011 16:55:42 +0300 [thread overview]
Message-ID: <4DEB8ADE.6070909@redhat.com> (raw)
In-Reply-To: <4de043641213294e72@agluck-desktop.sc.intel.com>
On 05/28/2011 03:35 AM, Luck, Tony wrote:
> [Oops - forgot to Cc: LKML!]
> Ingo wrote:
> > We already have a generic facility to do such things at
> > return-to-userspace: _TIF_USER_RETURN_NOTIFY.
>
> This is what it might look like if we replaced the current use
> of TIF_MCE_NOTIFY with TIF_USER_RETURN_NOTIFY in mce.c
>
> Question: the notifier can potentially send signals to the current
> process - so should the check for _TIF_USER_RETURN_NOTIFY in do_notify_resume
> be moved before the check for _TIF_SIGPENDING?
It is unnecessary. If a signal is raised, then _TIF_SIGPENDING will be
ORed into the flags, and when we try to return again, we'll notice it
and go right back into do_notify_resume().
> Would doing do be a problem
> for the existing user of user-return-notifiers (kvm)?
It would not be a problem. The orders of the checks should be immaterial.
<snip patch>
Looks good.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-06-05 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 0:35 [POC] mce: replace TIF_MCE_NOTIFY with TIF_USER_RETURN_NOTIFY Luck, Tony
2011-06-05 13:55 ` Avi Kivity [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=4DEB8ADE.6070909@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
/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.