Xen devel - Oct 2007 - c/s 15147 change to struct vcpu_register_vcpu_info

This changeset changed the layout of the structure, and 3.1 as well as
2.6.23 use the old layout, while 3.1.1 uses to new one. I''m also
puzzled
about the need for an MFN to be uint64_t rather than xen_pfn_t.

Thanks for clarification,
Jan


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

Xen 3.1.0 does not support that vcpu operation. 3.1.1 is the first stable
Xen release to support it. The old definition in 2.6.23 is a bug, and I
believe Jeremy already has a fix for 2.6.24.

The structure re-definition was to allow extensibility and to avoid having
to implement 32-on-64 shim code.

 -- Keir

On 18/10/07 14:02, "Jan Beulich" <jbeulich@novell.com> wrote:
> This changeset changed the layout of the structure, and 3.1 as well as
> 2.6.23 use the old layout, while 3.1.1 uses to new one. I''m also
puzzled
> about the need for an MFN to be uint64_t rather than xen_pfn_t.
> 
> Thanks for clarification,
> Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


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

Keir Fraser wrote:
> Xen 3.1.0 does not support that vcpu operation. 3.1.1 is the first stable
> Xen release to support it. The old definition in 2.6.23 is a bug, and I
> believe Jeremy already has a fix for 2.6.24.
>   
Yes, that''s in now.   But I''m seeing guests hang mysteriously
when they
use register_vcpu_info now...

    J

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