mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jinsong Liu <jinsong.liu@intel.com>,
	Will Auld <will.auld@intel.com>, Tony Luck <tony.luck@intel.com>,
	"Keir (Xen.org)" <keir@xen.org>, Ashok Raj <ashok.raj@intel.com>,
	Yunhong Jiang <yunhong.jiang@intel.com>,
	Susie Li <susie.li@intel.com>,
	Haitao Shan <haitao.shan@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Donald D Dugger" <donald.d.dugger@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Xiantao Zhang <xiantao.zhang@intel.com>
Subject: Re: [Xen-devel] [xen vMCE RFC V0.2] xen vMCE design
Date: Thu, 28 Jun 2012 10:58:33 +0100	[thread overview]
Message-ID: <1340877513.10942.23.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4FEC463E020000780008C6A7@nat28.tlf.novell.com>

On Thu, 2012-06-28 at 10:55 +0100, Jan Beulich wrote:
> >>> On 28.06.12 at 11:40, "Liu, Jinsong" <jinsong.liu@intel.com> wrote:
> > So I would like to push new vMCE as quickly as possible. What's the timeline 
> > of vMCE developing that xen 4.2 could accept?
> 
> Weeks ago, really. See http://lists.xen.org/archives/html/xen-devel/2012-06/msg01619.html
> and follow-ups - we'd really only consider getting the save/restore
> interface into forward compatible shape as acceptable.

Yes it really is far to late to considering entire new features at this
stage.

Ian.

> 
> > I wonder if we could make major 
> > components of vMCE done before xen 4.2 timeline, and leave the surrounding 
> > features and the corner cases done later?
> 
> Unfortunately it's likely going to be even less. However, if split
> that way, chances are things could go into e.g. 4.2.1.
> 
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



  reply	other threads:[~2012-06-28  9:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  3:51 Liu, Jinsong
2012-06-27 13:14 ` Jan Beulich
2012-06-28  8:54   ` Liu, Jinsong
2012-06-28  9:08     ` Jan Beulich
2012-06-28  9:40       ` Liu, Jinsong
2012-06-28  9:55         ` Jan Beulich
2012-06-28  9:58           ` Ian Campbell [this message]
2012-06-28 13:38           ` Liu, Jinsong
2012-06-28 14:00             ` Jan Beulich
2012-06-28 17:02               ` Liu, Jinsong
2012-06-29  9:58                 ` [Xen-devel] " Christoph Egger
2012-07-02 17:32                   ` Liu, Jinsong
2012-07-03  7:16                     ` Jan Beulich
2012-07-03  9:45                       ` Christoph Egger
2012-07-03 13:26                       ` Luck, Tony
2012-07-03 14:50                         ` Christoph Egger
2012-07-03 15:08                           ` Jan Beulich
2012-07-03 15:33                             ` 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=1340877513.10942.23.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ashok.raj@intel.com \
    --cc=donald.d.dugger@intel.com \
    --cc=haitao.shan@intel.com \
    --cc=jinsong.liu@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=susie.li@intel.com \
    --cc=tony.luck@intel.com \
    --cc=will.auld@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiantao.zhang@intel.com \
    --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

all inboxes | Powered by JetHome®