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

Re: [Xen-devel] arm: How DomU access to iomem is implemented

To: Andrii Anisov <andrii.anisov@xxxxxxxxxxxxxxx>
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Mon, 10 Jun 2013 17:19:56 +0100
Cc: Julien Grall <julien.grall@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Mon, 10 Jun 2013 16:20:21 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Mon, 10 Jun 2013, Andrii Anisov wrote:
> Julien,
> Thank you for answer.
> As I understand with HW IRQ routing the situation is pretty the same?

Yes, that's correct. When we do implement device assignment we'll have
to go through all these issues.  I expect we'll end up writing something
like xc_physdev_map_pirq/PHYSDEVOP_map_pirq.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] arm: How DomU access to iomem is implemented
  - From: Andrii Anisov

References:
- [Xen-devel] arm: How DomU access to iomem is implemented
  - From: Andrii Anisov
- Re: [Xen-devel] arm: How DomU access to iomem is implemented
  - From: Julien Grall
- Re: [Xen-devel] arm: How DomU access to iomem is implemented
  - From: Andrii Anisov

Prev by Date: Re: [Xen-devel] Xen 4.3 development update
Next by Date: Re: [Xen-devel] Xen 4.3 development update
Previous by thread: Re: [Xen-devel] arm: How DomU access to iomem is implemented
Next by thread: Re: [Xen-devel] arm: How DomU access to iomem is implemented
Index(es):
- Date
- Thread

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