xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: "Liu, Jinsong" <jinsong.liu@intel.com>,
	Jan Beulich <JBeulich@suse.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Auld, Will" <will.auld@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	xen-devel <xen-devel@lists.xen.org>,
	"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: Re: [PATCH] Xen/MCE: adjust for future new vMCE model
Date: Thu, 05 Jul 2012 09:55:49 +0100	[thread overview]
Message-ID: <CC1B1525.44BF1%keir@xen.org> (raw)
In-Reply-To: <DE8DF0795D48FD4CA783C40EC829233528AD85@SHSMSX101.ccr.corp.intel.com>

On 05/07/2012 08:50, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:

>> 
>> We're currently saving MCG_CAP, with the bank count in it
>> reflecting the host bank count, and with other bits in there also
>> matching the host's. That's what we'd like to simplify, _but_ as
>> said we're already shipping the current interface, so backward
>> compatibility will be needed anyway.
>> 
>> The main issue really was with MCi_CTL, which if not saved by
>> 4.2 wouldn't be restorable in 4.3. Now that we decided that they
>> will get fixed values anyway, simply enforcing these fixed values
>> (to not surprise the guest) would seem sufficient for 4.2. MCi_CTL2
>> are different in that afaiu setting them to 0 for a guest with no
>> saved values (i.e. 4.2, where their presence isn't being advertised,
>> since CMCI doesn't get surfaced) would be correct.
>> 
>> Jan
> 
> So Jan and Ian, do we really care migrate N -> N-1 ?
> If yes, I will save/restore MCi_CTL2, but that would involve more code change.

We categorically do not care about migration N -> N-1. N-1 -> N is the only
thing that really gets much test (N-k -> N should work by design though),
and it's the most useful one, for rolling fairly-seamless upgrades.

 -- Keir

  reply	other threads:[~2012-07-05  8:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 13:08 [PATCH] Xen/MCE: adjust for future new vMCE model Liu, Jinsong
2012-07-04 13:25 ` Christoph Egger
2012-07-04 16:08   ` Liu, Jinsong
2012-07-05  7:00     ` Jan Beulich
2012-07-05  9:18       ` Christoph Egger
2012-07-05  9:36         ` Liu, Jinsong
2012-07-05  9:53           ` Christoph Egger
2012-07-05  9:58           ` Christoph Egger
2012-07-05 10:17             ` Liu, Jinsong
2012-07-05 17:01     ` Luck, Tony
2012-07-05 18:38       ` Liu, Jinsong
2012-07-05 20:08         ` Luck, Tony
2012-07-06  9:12         ` Christoph Egger
2012-07-06 10:13           ` Jan Beulich
2012-07-04 13:37 ` Ian Campbell
2012-07-04 14:11   ` Jan Beulich
2012-07-04 13:40 ` Jan Beulich
2012-07-05  3:03   ` Liu, Jinsong
2012-07-05  6:39     ` Jan Beulich
2012-07-05  6:44       ` Ian Campbell
2012-07-05  7:02         ` Ian Campbell
2012-07-05  7:19           ` Jan Beulich
2012-07-05  7:50             ` Liu, Jinsong
2012-07-05  8:55               ` Keir Fraser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-05  3:30 Liu, Jinsong
2012-07-05  6:36 ` Jan Beulich
2012-07-05  7:28   ` Liu, Jinsong
2012-07-05  7:42     ` Jan Beulich
2012-07-05  6:52 ` Jan Beulich
2012-07-05  9:20   ` Liu, Jinsong
2012-07-05 10:43     ` Ian Campbell
2012-07-05 12:04       ` Liu, Jinsong
2012-07-05 17:18         ` Luck, Tony
2012-07-05 18:47           ` Liu, Jinsong
2012-07-05 11:40     ` Jan Beulich
2012-07-05 12:46       ` Liu, Jinsong
2012-07-05 13:33         ` Jan Beulich
2012-07-05 15:56           ` Liu, Jinsong
2012-07-05 16:04             ` Jan Beulich
2012-07-05 16:42               ` Liu, Jinsong
2012-07-06  8:07                 ` Jan Beulich
2012-07-05 13:39     ` Christoph Egger

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=CC1B1525.44BF1%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jinsong.liu@intel.com \
    --cc=tony.luck@intel.com \
    --cc=will.auld@intel.com \
    --cc=xen-devel@lists.xen.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).