From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Li, Xin" <xin.li@intel.com>,
"Li, Haicheng" <haicheng.li@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Gianluca Guida <gianluca.guida@eu.citrix.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: Weekly VMX status report. Xen: #18846 & Xen0: #749
Date: Tue, 16 Dec 2008 12:29:53 +0000 [thread overview]
Message-ID: <C56D4FC1.EA0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E88DD564E9DC5446A76B2B47C3BCCA15432C0FC2@pdsmsx503.ccr.corp.intel.com>
On 16/12/2008 12:18, "Li, Xin" <xin.li@intel.com> wrote:
>> Applied to Xen-unstable as c/s 18922.
>>
>> Do we need this for 3.3 as well? And what about 3.2?
>>
>
> 3.3 needs it, but 3.2 may not, as this crash is introduced by 17781. But an
> evil guest may crash a Xen 3.2 hypervisor...
Yes, I think it is probably needed really.
-- Keir
next parent reply other threads:[~2008-12-16 12:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E88DD564E9DC5446A76B2B47C3BCCA15432C0FC2@pdsmsx503.ccr.corp.intel.com>
2008-12-16 12:29 ` Keir Fraser [this message]
2008-12-16 12:33 ` Weekly VMX status report. Xen: #18846 & Xen0: #749 Li, Xin
[not found] <E88DD564E9DC5446A76B2B47C3BCCA1540A67C2A@pdsmsx503.ccr.corp.intel.com>
2008-12-07 8:41 ` Keir Fraser
2008-12-08 3:00 ` Cui, Dexuan
2008-12-12 20:37 ` Gianluca Guida
2008-12-12 23:22 ` Keir Fraser
2008-12-12 23:30 ` Gianluca Guida
2008-12-13 14:06 ` Keir Fraser
2008-12-13 15:14 ` Nakajima, Jun
2008-12-13 15:40 ` Keir Fraser
2008-12-13 22:43 ` Nakajima, Jun
2008-12-13 23:21 ` Keir Fraser
2008-12-15 13:02 ` Keir Fraser
2008-12-16 5:54 ` Li, Haicheng
2008-12-16 7:24 ` Li, Haicheng
2008-12-16 11:55 ` Keir Fraser
2008-12-06 11:45 Li, Haicheng
2008-12-06 12:16 ` Keir Fraser
2008-12-06 12:21 ` Li, Haicheng
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=C56D4FC1.EA0%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=gianluca.guida@eu.citrix.com \
--cc=haicheng.li@intel.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@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 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.