From: Andi Kleen <andi@firstfloor.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>,
Liping Ke <liping.ke@intel.com>
Subject: Re: [pvops-dom0] Adding MCA logging support in pv_ops
Date: Fri, 31 Jul 2009 17:19:06 +0200 [thread overview]
Message-ID: <87ljm43mol.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4A7174D3020000780000D350@vpn.id2.novell.com> (Jan Beulich's message of "Thu, 30 Jul 2009 09:24:19 +0100")
"Jan Beulich" <JBeulich@novell.com> writes:
> Additionally, the new use of the space previously
> consumed by the res1 field seems to put under question whether that
> was actually forward compatible (namely, whether it might confuse
> newer user space tools).
It will, either by logging junk fields or if you're unlucky (and e.g. broke
the CPUID field) completely wrong output.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-31 15:19 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 [this message]
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=87ljm43mol.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=JBeulich@novell.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.