[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: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 26 Oct 2007 16:04:38 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 26 Oct 2007 08:05:34 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgXJpgKtuetZtZRSk2SPUOVajTGGQAieFwCAArETtAAAMMrGwAAXpSgAABdVMg=
  • Thread-topic: [Xen-devel] Re: [PATCH 0/5] Add MSI support to xen environment

On 26/10/07 16:02, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

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

Oh, I see. Then it probably has to be a phydevop and let dom0 kernel do it.
But there should be no reason to let domU use the map_irq physdev_op at all.

 -- Keir



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