[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4FEC463E020000780008C6A7@nat28.tlf.novell.com>
Date: Thu, 28 Jun 2012 10:55:42 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Jinsong Liu" <jinsong.liu@...el.com>,
"Will Auld" <will.auld@...el.com>
Cc: "Ashok Raj" <ashok.raj@...el.com>,
"Donald D Dugger" <donald.d.dugger@...el.com>,
"Haitao Shan" <haitao.shan@...el.com>,
"Jun Nakajima" <jun.nakajima@...el.com>,
"Susie Li" <susie.li@...el.com>, "Tony Luck" <tony.luck@...el.com>,
"Xiantao Zhang" <xiantao.zhang@...el.com>,
"Yunhong Jiang" <yunhong.jiang@...el.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Keir Fraser" <keir@....org>
Subject: RE: [xen vMCE RFC V0.2] xen vMCE design
>>> On 28.06.12 at 11:40, "Liu, Jinsong" <jinsong.liu@...el.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.
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists