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

RE: [Xen-devel] Re: [PATCH 0/5] Add MSI support to xen environment


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
  • Date: Fri, 26 Oct 2007 23:02:01 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 26 Oct 2007 08:02:57 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgXJpgKtuetZtZRSk2SPUOVajTGGQAieFwCAArETtAAAMMrGwAAXpSg
  • Thread-topic: [Xen-devel] Re: [PATCH 0/5] Add MSI support to xen environment

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx <> wrote:
> On 26/10/07 15:35, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
> 
>> For pciback to poke irq configuration, I think for IOAPIC irq is done
>> already, we only need add the mapping at that time. For MSI , domain
U
>> will do that dynamically, so not sure if viable, especially
considering
>> for MSI-x, only driver knows how many entry will be used.
> 
> dom0 needs to be involved, since we can't let domU map any arbitrary
vector
> into its pirq space. Since dom0 has to be involved in access control
to the
> irq vector space, can't it do the mapping?

yes, what I mean is, "before starting the domain" works for IOAPIC IRQ,
not MSI. MSI will still through communcation between PCI
frontend/backend directly.

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

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