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

Re: [Xen-devel] ACPI Xen and SMMU driver

On Wed, 2014-09-17 at 09:36 +0530, manish jaggi wrote:

Adding Naresh and Parth who are working on Xen ACPI support within

> Hi Stefano / Ian,
> Currently the SMMU code for ARM is derived from Linux SMMU code which
> is dependent on device tree. My current PCI passthrough work is based
> on the platform device passthrough support which is actually the
> device tree node pass through.
> With ACPI smmu.c have to be split into smmu-dt.c and smmu-acpi.c,
> smmu-ops.c. The smmu-ops would be much simpler driver.
> As PCI passthrough on ARM is only on ARMv8 servers

I don't think this is a true assumption (but I also don't think it makes
a difference to the approach we should take)

>  do you think it
> makes sense to provide the PCI passthrough support via acpi smmu
> driver  or we would have to still base it on (current)smmu-dt driver,
> when targeting for 4.5 Xen.

We certainly don't want to be duplicating the actual driver
functionality (I don't think you were suggesting that though).

What we will need is an ACPI equivalent of the "glue" bit (i.e.
DT_DEVICE_START and the functions it references). I think it remains to
be seen once ACPI patches start turning up but I hope that the glue
layer will be small enough that it can all live alongside the DT glue in
the smmu.c file, and perhaps even share some of the code between the DT
and ACPI glue.

If it turns out that the ACPI glue is a significant portion of the
smmu.c file then perhaps we will need to consider splitting it out, but
I'm hopeful it won't come to that.


Xen-devel mailing list



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