From: Christoph Egger <Christoph.Egger@amd.com>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: "jeremy@goop.org" <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [pvops-dom0] Adding MCA logging support in pv_ops
Date: Thu, 6 Aug 2009 09:27:04 +0200 [thread overview]
Message-ID: <200908060927.05183.Christoph.Egger@amd.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CE0B5E01@PDSMSX501.ccr.corp.intel.com>
On Thursday 06 August 2009 03:37:39 Ke, Liping wrote:
> Hi, Christoph
> Since we can't keep the same copy of header files for pv-ops and XEN
> already, When sync back the header to XEN, I will only sync back the
> modified comments and other required changes. As for the change for
> programming conventions (inline function vs micro), I will not put them
> back to XEN. Is it OK for you?
Yes, that's fine.
>
> As for the union structure for recovery action, since no one is using it
> now,I plan firstly to add a comment on it, something like "If more than
> one kind of recovery action perbank permited, union structure need to
> be changed". How do you think about it?
That's fine with me. Tnx.
Christoph
> Thanks a lot!
> Criping
>
> Christoph Egger wrote:
> > On Wednesday 05 August 2009 03:57:20 Ke, Liping wrote:
> >> Hi, Christoph
> >> Please see my below comments.
> >>
> >> And also, I found some interfaces are different in pv_ops kernel
> >> such as GUEST_HANDLE related. Seems we can't keep the same copy of
> >> common
> >> file between XEN and GUEST.
> >
> > That's not a problem as long as the ABI doesn't change.
> >
> >> We have to do slight changes to the XEN file before copying it to
> >> guest kernel.
> >
> > Well, the comment updates I suppose.
> >
> >> And also, for the header file, I modified a little according to
> >> Andi's feedback such as gigantic macros will be unacceptable
> >> according to kernel code conventions, etc. So I modify
> >> x86_mcinfo_lookup into inline function.
> >
> > NetBSD also has some "local" guest header changes which aren't
> > accepted
> > by Keir due to Xen conventions.
> > Keep in mind that you have to merge the headers whenever you sync up
> > with Xen.
> >
> >> I will resend the new patch to all of you for further feedback.
> >> After the patch is accepted, I will sync the modified head file back
> >> to XEN for consistency.
> >
> > Please practise friendly actions for non-Linux guests when changing
> > the headers. Changing the macros for only one guest isn't a friendly
> > action for all guests.
> >
> > Please only sync back the comment updates.
> >
> > If NetBSD, Solaris and Linux were trying to have all local changes in
> > Xen headers, they would become a mess.
> >
> >> Thanks a lot for your help!
> >> Criping
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-08-06 7:27 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
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 [this message]
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=200908060927.05183.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=jeremy@goop.org \
--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.