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

Re: [Xen-devel] [PATCH v2 00/21] xen/arm: Add support for non-pci passthrough



On Wed, 10 Sep 2014, Christoffer Dall wrote:
> >>   How does a user
> >> know which physical address in Xen's physical address space needs to
> >> be remapped based on the hardware description language for Dom0?
> >
> > This is an interesting question. The short answer for platform device
> > type things is "they just know" (they presumably have datasheets etc).
> > But I think the underlying question here is whether they are given in PA
> > space or dom0 IPA space, right?
> >
> 
> re. the underlying question, yes.
> 
> For platform devices, I think the "they just know" doesn't really
> work.

"Who" should "just know"? We are talking about users, specifically
embedded engineers trying to put together their systems. Certainly not a
server use case. A server sysadmin cannot be expected to "just know".
If we wanted to export this feature to end users we would have to
provide a simpler way to do it.


> There must be a way for user space to determine the IO
> addresses and IRQ numbers for a platform device, I just think it
> should be completely decoupled from ACPI and DT.

I don't follow you here. How would a user find the info she needs on a
device without using an ACPI/DT identifier to reference it?

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


 


Rackspace

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