public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Borislav Petkov <bp@amd64.org>,
	Chen Gong <gong.chen@linux.intel.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: x86, mce, Use user return notifier in mce
Date: Fri, 13 Jan 2012 14:32:32 +0800	[thread overview]
Message-ID: <1326436352.8294.22.camel@yhuang-dev> (raw)
In-Reply-To: <CA+8MBbJHsOHb-COG_y36VYDA9EeTs3KpLc86kw1OhVF9Z_p7Jw@mail.gmail.com>

On Thu, 2012-01-12 at 17:46 -0800, Tony Luck wrote:
> On Thu, Jan 12, 2012 at 4:36 PM, Huang Ying <ying.huang@intel.com> wrote:
> > Replace the home-made TIF_MCE_NOTIFY based code in MCE with user
> > return notifier.
> 
> When I looked at this before, I found that the existing user return notifier had
> the meaning "call a function before THIS CPU returns to user space". Use in KVM
> was to update some MSR that needed adjustment before a cpu ran another user
> process.
> 
> The MCE code wanted something slightly different: "call a function before THIS
> PROCESS returns to user space". So my prototype code from last year made a
> whole new set of interfaces - similar in style to the user return
> notifier, but with
> the MCE semantics.
> 
> At first glance it looks like you are just using the user return
> notifier code (perhaps
> I'm mis-reading the diff?). This won't work - it's possible for a
> context switch, and
> then the process that hit the MCE may get moved to another cpu, when it will
> be run. Meanwhile we'll execute our function in the context of some
> other process.

You are right.  User return notifier can not be used for SRAR.  I think
that may be useful for SRAO.  Where we need a way to do notify earlier
in case of the corresponding work_queue item is not executed in time.

Best Regards,
Huang Ying



  reply	other threads:[~2012-01-13  6:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  0:36 x86, mce, Use user return notifier in mce Huang Ying
2012-01-13  0:36 ` [RFC 1/2] urn, make user return notifier lockless Huang Ying
2012-01-13  0:36 ` [RFC 2/2] x86, mce, Use user return notifier in mce Huang Ying
2012-01-13  1:46 ` Tony Luck
2012-01-13  6:32   ` Huang Ying [this message]
2012-01-13  7:41     ` Tony Luck
2012-01-16  1:21       ` Huang Ying
2012-01-20 17:34         ` Tejun Heo
2012-01-21  2:44           ` Huang Ying
2012-01-21  5:56             ` Tejun Heo
2012-01-21  6:19               ` Huang Ying
2012-01-23 23:00                 ` Luck, Tony
2012-01-24 14:39       ` Avi Kivity

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=1326436352.8294.22.camel@yhuang-dev \
    --to=ying.huang@intel.com \
    --cc=bp@amd64.org \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox