| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749
|
To: |
Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Li, Haicheng" <haicheng.li@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, Gianluca Guida <gianluca.guida@xxxxxxxxxxxxx> |
|
Subject: |
RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749 |
|
From: |
"Li, Xin" <xin.li@xxxxxxxxx> |
|
Date: |
Tue, 16 Dec 2008 20:33:33 +0800 |
|
Accept-language: |
en-US |
|
Acceptlanguage: |
en-US |
|
Cc: |
"'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|
Delivery-date: |
Tue, 16 Dec 2008 04:34:20 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<C56D4FC1.EA0%keir.fraser@xxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<E88DD564E9DC5446A76B2B47C3BCCA15432C0FC2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C56D4FC1.EA0%keir.fraser@xxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
Thread-index: |
AcldK/fZZNTFfVr6k0WK9hRQshPOTwAAZfOQAALnZR0ADcmHgABRQwZvACMnlFAAAwoSIAAJvz8LAACJN+AAAK3GJwAAG5sA |
|
Thread-topic: |
[Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749 |
>>> 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.
Agree!
-Xin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, (continued)
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Nakajima, Jun
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Nakajima, Jun
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Li, Haicheng
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Li, Haicheng
- Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
Re: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749, Keir Fraser
- RE: [Xen-devel] Weekly VMX status report. Xen: #18846 & Xen0: #749,
Li, Xin <=
|
|
|
| |
|
Home