Re: Xen 4.0.0x allows for data corruption in Dom0

[Keir Fraser <keir.fraser@eu.citrix.com>]

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

On 09/03/2010 10:25, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:

>>> How about these being vcpu_time_info structures? The fields
>>> appear to all make sense. The only thing not matching this would
>>> be a few differently looking corruption entries sent earlier by Joanna,
>>> so this may not be the only thing. But it would explain why with 3.4.2
>>> the issue is not present.
>> 
>> Pasi, can you try the attached patch (which simply stubs out the new
>> VCPUOP_register_vcpu_time_memory_area hypercall)?
> 
> Yeah, but there's no patch attached ;)

Good point. Attached now!

 K.


[-- Attachment #2: 00-disable-vcpu-time --]
[-- Type: application/octet-stream, Size: 413 bytes --]

diff -r e6f751ed8e38 xen/arch/x86/domain.c
--- a/xen/arch/x86/domain.c	Tue Mar 09 10:00:37 2010 +0000
+++ b/xen/arch/x86/domain.c	Tue Mar 09 10:12:30 2010 +0000
@@ -970,6 +970,7 @@
         break;
     }
 
+#if 0
     case VCPUOP_register_vcpu_time_memory_area:
     {
         struct vcpu_register_time_memory_area area;
@@ -988,6 +989,7 @@
 
         break;
     }
+#endif
 
     case VCPUOP_get_physid:
     {

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel