From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Ke, Liping" <liping.ke@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs
Date: Wed, 24 Dec 2008 08:01:39 +0000 [thread overview]
Message-ID: <C5779CE3.20892%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401C4CA8A39@PDSMSX501.ccr.corp.intel.com>
On 24/12/2008 02:57, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
> As for your proposal of do it before the stop_machine_run(), it may reduce the
> window, but still can't eliminate the window of lost CMCI interrupt, unless we
> do similar thing in the cmci_cpu_down() (i.e. all CPU is irq_disabled before
> update the CMCI status). It is the same if we pull the notifier chain to Xen.
> How is your idea?
You only need hardirqs disabled, so rendezvous within an on_each_cpu()
callback is sufficient for you. You don't need to get intimate with
stop_machine_run()!
-- Keir
next prev parent reply other threads:[~2008-12-24 8:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 3:54 [patch 0/3]Enable CMCI (Corrected Machine Check Error Interrupt) for Intel CPUs Ke, Liping
2008-12-22 12:06 ` Keir Fraser
2008-12-23 5:17 ` Ke, Liping
2008-12-23 8:40 ` Keir Fraser
2008-12-23 9:00 ` Keir Fraser
2008-12-23 12:32 ` Ke, Liping
2008-12-24 2:57 ` Jiang, Yunhong
2008-12-24 8:01 ` Keir Fraser [this message]
2008-12-24 8:46 ` Jiang, Yunhong
2008-12-24 8:54 ` Keir Fraser
2008-12-24 14:51 ` Jiang, Yunhong
2008-12-24 14:55 ` Keir Fraser
2008-12-24 15:08 ` Jiang, Yunhong
2008-12-24 15:38 ` Keir Fraser
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=C5779CE3.20892%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=liping.ke@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@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.