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>, Tejun Heo <tj@kernel.org>
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: Mon, 16 Jan 2012 09:21:15 +0800	[thread overview]
Message-ID: <1326676875.8294.30.camel@yhuang-dev> (raw)
In-Reply-To: <CA+8MBb+oqJZDYvmh8E6RB2MRp5fDj298Qjc4zs-rmyGkA4F3cw@mail.gmail.com>

On Thu, 2012-01-12 at 23:41 -0800, Tony Luck wrote:
> On Thu, Jan 12, 2012 at 10:32 PM, Huang Ying <ying.huang@intel.com> wrote:
> > 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.
> 
> OK - I've been so focused on SRAR that I didn't think of the SRAO case.
> But even there it seems odd to use user return notifier. We'd like the
> SRAO work item to be executed promptly - but we don't care where it
> is executed. So the "execute on this cpu" part of user return notifiers
> doesn't quite fit.
> 
> Is there a concept of "high priority work queue"?

"high priority work queue" sounds like a good idea.

Hi, Tejun,

Do you think the concept of "high priority work queue" is possible?
This is the requirement from our RAS guys.  To make some hardware
recovery function to be executed ASAP in process context.

Best Regards,
Huang Ying



  reply	other threads:[~2012-01-16  1:21 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
2012-01-13  7:41     ` Tony Luck
2012-01-16  1:21       ` Huang Ying [this message]
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=1326676875.8294.30.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=tj@kernel.org \
    --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