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

Re: [Xen-devel] irq_guest_eoi_timer interaction with MSI

  • To: Jan Beulich <jbeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 25 Nov 2008 08:44:11 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 25 Nov 2008 00:44:28 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclO2fygOvXxFLrNEd2bbAAWy6hiGQ==
  • Thread-topic: [Xen-devel] irq_guest_eoi_timer interaction with MSI

On 25/11/08 08:40, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>>> But just as map_domain_page(), map_domain_page_global() can't be used
>>> out of IRQ context...
>> I would have kept the page mapped from when it was registered until domain
>> death. Same as we do for guest-registered vcpu_info.
> Oh, I indeed didn't consider that option. The question is - does it scale?
> 2Mb doesn't seem all that much for a global pool, but otoh it's perhaps
> unlikely that 32-bit hypervisors would have to manage too large an
> amount of domains/vCPU-s. So yes, I'll go that route.

Yeah, exactly. Anyone who wants a larger number of domains/VCPUs probably
has 64-bit-capable hardware. And lack of 64-bit capability is the only
reason not to run 64-bit Xen these days.

 -- Keir

Xen-devel mailing list



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