[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: Rebased xen-ia64 tree with VT-i support


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 20 May 2005 14:39:22 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 20 May 2005 06:38:46 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVb56iXO9CXozwzTtq2vxDCqWHCJgAB8D0AAAeREcAAHnJcIAARiYrgAA4j91A=
  • Thread-topic: [Xen-ia64-devel] RE: Rebased xen-ia64 tree with VT-i support

>
>But as a note, the patch to system.h and processor.h will still exist
>which may simply remove original definition and include "xen_***"
>specific header to contain new definition. The reason is the difficulty
>to handle multiple redefinitions without any change to original file.
>But that patch will be stable, and later changes only happen in
>"xen_***" as you expected.
>

Hi, Dan,
        Just a small correction. I shouldn't mean remove any original
content, but actually say adding protection to original definition by
"#ifndef XEN" if xen specific version is needed, to reduce patch size in
current model. :) You can check the change in staging tree.

Thanks,
Kevin

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.