From: Frank Van Der Linden <Frank.Vanderlinden@Sun.COM>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH 0/6 ] MCE: patches clean-up and fixing bugs
Date: Thu, 28 Jan 2010 08:37:30 -0700 [thread overview]
Message-ID: <4B61AF3A.9000301@Sun.COM> (raw)
In-Reply-To: <C8EDE645B81E5141A8C6B2F73FD9265117C58A3361@shzsmsx501.ccr.corp.intel.com>
Jiang, Yunhong wrote:
> This series patches clean-up and fixing some bugs for MCE handler. Most of them are quite minor, except the vmsr.patch.
>
> Patch 1: bank.patch: Handle the virtual MCE MSR bank access correctly.
>
> Patch 2: vmsr.patch: Not GP fault when guest write non 0s or 1s to MCA CTL MSRs.
>
> Patch 3: put_domain.patch: put domain in mce action.
>
> Patch 4: mca_add_trans.patch: Fix the vMCE address translation for HVM guest.
>
> Patch 5: broadcast.patch: Add MCE broadcast checkiing.
>
> Patch 6: mce_printk.patch: Be more careful for printk in mce context.
>
>
Thanks for the patches! Aside from the comments Christoph already made,
these look good to me. Thanks for also including the mce_is_broadcast
part, that fixes injection on NHM-EX.
It would be good to re-integrate the mcheck handler for AMD and Intel,
but as you said, you have a patch lined up for that, and that can be
done in the future.
- Frank
next prev parent reply other threads:[~2010-01-28 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 5:55 [PATCH 0/6 ] MCE: patches clean-up and fixing bugs Jiang, Yunhong
2010-01-28 15:37 ` Frank Van Der Linden [this message]
2010-01-29 2:49 ` Jiang, Yunhong
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=4B61AF3A.9000301@Sun.COM \
--to=frank.vanderlinden@sun.com \
--cc=Christoph.Egger@amd.com \
--cc=JBeulich@novell.com \
--cc=keir.fraser@eu.citrix.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.