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

Re: [Xen-devel] [PATCH 16/16] HACK: xen: arm: map PCI controller ranges region MMIOs to dom0.

On Thu, 2013-11-21 at 15:42 +0000, Julien Grall wrote:
> On 11/21/2013 02:57 PM, Ian Campbell wrote:
> > On Thu, 2013-11-21 at 14:32 +0000, Julien Grall wrote:
> >>
> >> On 11/20/2013 02:48 PM, Ian Campbell wrote:
> >>> The ranges property of a node with device_type = "pci" is defined in ePAPR
> >>> 2.3.8. Map the appropriate MMIO regions through to dom0.
> >>>
> >>> This is a hack/PoC since it actually crashes for some reason. Hence it
> >>> contains a hacked in hardcoded list suitable for Xgene while I figure this
> >>> out.
> >>>
> >>> This should also eventually handle the interrupt-map and (ePAPR 
> >>> and
> >>> possibly dma-ranges (ePAPR 2.3.9) and msi-ranges (unspeciifed?) too.
> >>
> >>
> >> For pci ranges, you can add a new bus in dt_bues. So you won't need
> >> specific code in domain_build.c and we will be able to use it later.
> >> You can take a look to linux/drivers/of/address.c
> >
> > Won't we still need to handle the resulting extra MMIO addresses which
> > are not part of the reg region?
> Which MMIO addresses are you talking about? I though all the ranges are 
> described by "reg"?

Please check ePAPR 2.3.8 -- the ranges property is used in bus nodes to
define the MMIO regions used by the child devices on that bus. The reg
property only covers the MMIO used by the bus controller itself.

The interrupts-map is similar.

> If the modification is too hard to implement for Xen 4.4, you can 
> implement specific_mapping callback for APM.

Yes, this is what I proposed already and am looking into.


Xen-devel mailing list



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