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

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


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Mon, 20 Jun 2005 13:38:57 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 20 Jun 2005 05:38:00 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVt1R72epaDDPsFSDugojimaqWWzAE1fZRAAAtgCqAAHuBxIACA1lmw
  • Thread-topic: [Xen-devel] Please pull latest xen-ia64.bkbits (CONFIG_VTI broken)

>-----Original Message-----
>From: Magenheimer, Dan (HP Labs Fort Collins)
>[mailto:dan.magenheimer@xxxxxx]
>Sent: Friday, June 17, 2005 11:52 PM
>
>Argh, I had test-compiled CONFIG_VTI with these but had neglected
>to "bk new" them.  (Apparently "bk patch" doesn't automatically
>do a new.)
>
>They are now pushed to xen-ia64.bkbits and it doesn't appear
>that Keir has pulled any of the changesets into xen.bkbits yet.
>
>Sorry, I'll try to be more careful in the future.

Thanks, and I'll also include a brief line about new files in patch
later, to save your time for filtering which files should be "bk new"
specifically.

>
>Note also that I've pushed an evtchn fix from Matt and your
>get_page_type/etc patch.  I don't think either of those impact
>CONFIG_VTI yet though.
>

Yes, CONFIG_VTI still works, but with potential impact. :)
        Since #ifdef CONFIG_VTI is used in put_page, you may also want
to use same format in get_page, instead of #ifdef 0. Or else put_page
and get_page are unsymmetrical on refcnt when CONFIG_VTI is enabled.

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®.