From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "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: Thu, 30 Jul 2009 10:14:32 -0700 [thread overview]
Message-ID: <4A71D4F8.70804@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CDF65C35@PDSMSX501.ccr.corp.intel.com>
On 07/30/09 02:23, Ke, Liping wrote:
> Hi, Jan
>
> I also noticed that in .31, several important missing field such as apic_id,
> socket id is added. Those field is better to be filled too.
> Since now pv_ops is based on .30, those changes haven't happen yet.
>
> So what's your suggestion? Seems we have to keep the old code and make
> a patch to it when .31 is supported in pv_ops?
>
The "rebase/master" branch is based on 2.6.31-rc4. It looks like your
patch doesn't really have any other code-level dependencies on the dom0
changes, so you could just base it on upstream 2.6.31-rc4.
J
next prev parent reply other threads:[~2009-07-30 17:14 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 [this message]
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
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=4A71D4F8.70804@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.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.