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

RE: [Xen-devel] spurious interrupts


  • To: "Jan Beulich" <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 12 Apr 2006 22:00:30 +0800
  • Delivery-date: Wed, 12 Apr 2006 07:01:16 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcZeNkWGOCU2b7oNRSeUIsluRwKoiwAAYGoA
  • Thread-topic: [Xen-devel] spurious interrupts

>From: Jan Beulich
>Sent: 2006年4月12日 21:37
>
>Finally, sufficiently unrelated, I wonder whether
>xen_create_contiguous_region() (or its caller(s)) shouldn't special
>case order being zero, as it seems pointless to go through numerous
>hypercalls in that case.
>

The question is that corresponding gmfns is not necessarily contiguous.
Maybe instead of setting order to non-zero, we can change nr_extents
to >1 by allocating buffer to contain all gmfns to be released.

Another abstraction could be to incorporate set_phys_to_machine
into decrease/increase_reservation, and thus allow 
xen_create_contiguous_region to be used by auto_translated_mode if
we want that translated mode to work for backend like for xen/ia64...

Thanks,
Kevin

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


 


Rackspace

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