[Xen-ia64-devel] RE: [Xen-devel] Please pull latest xen-ia64.bkbits (CONFIG_VTI broken)

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Oops, two important files are missed in your changeset 1.1709.1.12.
(mm.c and vmx_hypercall.c) which are included in patch[3/3] sent out
yesterday.

Please add those two files to bk repository, or else VTI build can't
pass compilation and it's not ia64-stable then. :)

Thanks,
Kevin
>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Magenheimer,
>Dan (HP Labs Fort Collins)
>Sent: Friday, June 17, 2005 3:52 AM
>
>
>Please pull bk://xen-ia64.bkbits.net/xeno-unstable-ia64.bk.
>Please also tag this with ia64-stable due to a critical bug fix.
>
>All xeno-unstable.bk changes through 1.1725 (serial_getc locking)
>have been merged and tested.
>
>Note that a couple of changesets affect non-ia64 files to
>separate out minor arch-dep functionality from core files
>and to link in a common file previously excluded.
>
>New xen-ia64 changesets include:
>- critical virtual mapping bug fix (much better stability)
>- change of Xen virtual address space for uncached addresses
>- various minor fixes preparing for multi-domain
>- various minor performance improvements for paravirtualized
>- get_page/put_page implementation
>- dom_mem_ops support
>- switch to different physical->machine mapping for VTI
>- new hypercall support for VTI
>
>Thanks,
>Dan
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel

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