From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "Kleen, Andi" <andi.kleen@intel.com>,
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: [pvops-dom0] Adding MCA logging support in pv_ops
Date: Fri, 07 Aug 2009 11:07:35 -0700 [thread overview]
Message-ID: <4A7C6D67.7090202@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CE0B6567@PDSMSX501.ccr.corp.intel.com>
On 08/06/09 19:32, Ke, Liping wrote:
> Hi, Jeremy and all
>
> This is the new formated patch and I have tried linux patch format check tools on it.
>
Thanks. I have a couple of little comments:
* when referring to Xen hg changesets, use the hex changeset ID
rather than the number, since the number only makes sense locally
(ie, your change 902 may not match anyone else's)
* don't put "dom0" in the driver filename; drivers/xen/mce.c is
enough. Same with the various symbols and messages mentioning dom0.
* don't use "#if define" if #ifdef would do; but try to avoid #ifdef
anyway. In particular, this *definitely* shouldn't be duplicating
code between the #if and #else blocks. At the very least, you
should just need one #ifdef to re-add the MCE/MCA flags back into
the mask.
+#if !defined(CONFIG_XEN_MCE)
cpuid_leaf1_edx_mask =
~((1 << X86_FEATURE_MCE) | /* disable MCE */
(1 << X86_FEATURE_MCA) | /* disable MCA */
(1 << X86_FEATURE_PAT) | /* disable PAT */
(1 << X86_FEATURE_ACC)); /* thermal monitoring */
-
+#else
+ cpuid_leaf1_edx_mask =
+ ~((1 << X86_FEATURE_PAT) | /* disable PAT */
+ (1 << X86_FEATURE_ACC)); /* thermal monitoring */
+#endif
Also, if you include the patch inline it makes it easier to review and
comment on.
Thanks,
J
next prev parent reply other threads:[~2009-08-07 18:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 5:15 [pvops-dom0] Adding MCA logging support in pv_ops Ke, Liping
2009-07-30 8:24 ` Jan Beulich
2009-07-30 8:45 ` Ke, Liping
2009-07-30 9:23 ` Ke, Liping
2009-07-30 17:14 ` Jeremy Fitzhardinge
2009-08-05 2:13 ` Ke, Liping
2009-08-05 22:55 ` Jeremy Fitzhardinge
2009-08-07 2:32 ` Ke, Liping
2009-08-07 18:07 ` Jeremy Fitzhardinge [this message]
2009-08-10 3:08 ` Ke, Liping
2009-08-13 20:55 ` Jeremy Fitzhardinge
2009-08-18 9:02 ` Jan Beulich
2009-08-18 9:25 ` Ke, Liping
2009-08-18 17:51 ` Jeremy Fitzhardinge
2009-08-19 1:25 ` Ke, Liping
2009-08-19 1:31 ` Ke, Liping
2009-08-05 2:54 ` Ke, Liping
2009-08-05 2:57 ` Ke, Liping
2009-07-31 15:19 ` Andi Kleen
2009-07-30 9:57 ` Christoph Egger
2009-08-05 1:57 ` Ke, Liping
2009-08-05 9:16 ` Christoph Egger
2009-08-06 1:37 ` Ke, Liping
2009-08-06 7:27 ` Christoph Egger
2009-08-06 8:49 ` Christoph Egger
2009-08-07 1:48 ` Ke, Liping
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=4A7C6D67.7090202@goop.org \
--to=jeremy@goop.org \
--cc=Christoph.Egger@amd.com \
--cc=JBeulich@novell.com \
--cc=andi.kleen@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=liping.ke@intel.com \
--cc=xen-devel@lists.xensource.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.