Re: [Xen-devel] [PATCH v2 32/41] arm : acpi dynamically map mmio regions

[Julien Grall <julien.grall@xxxxxxxxxx>]

Hi,

On 30/07/15 19:02, Parth Dixit wrote:
>                     instead of getting mmio information for individual
> devices from dsdt, we will map all the non-ram regions described in
> uefi. AML interpreter option was discussed earlier and it was decided
> not to go with that approach. You can find more details in the linaro
> xen wiki for the reasoning behind it.

Which page are you talking about? I only found [1] speaking about ACPI.
Although, there is nothing related to MMIO mapping.

Anyway, it's not possible to get the list of MMIOs regions for the UEFI
System Memory Map (see the mail you forward on the ML [2]).

Although, based on the RAM region we could deduce a possible set of MMIO
regions. It would be fine to mapped unused region in memory and we could
take advantage of super page.

While you are speaking about the wiki page. Can one of you update the
wiki page about the boot protocol? Jan had some concerns about the
solution you choose (see [3] to not mention the whole thread).

We need to agree on the boot protocol before going further on this series.

To speed up the upstreaming process, it would be nice if you start a
thread about the boot protocol for ACPI with relevant people in CCed.
The main goal will be to explain why you choose this way. This will be
the base to talk about improvement and/or answer concerns for other people.

FWIW, Jan also suggested a different boot protocol based on the x86 one.
It may be good for you to see whether it would fit ACPI on ARM.

Regards,

[1] https://wiki.linaro.org/LEG/Engineering/Virtualization/ACPI_on_Xen

[2]
http://lists.xenproject.org/archives/html/xen-devel/2015-06/msg02059.html

[3] http://lists.xen.org/archives/html/xen-devel/2015-05/msg02736.html

-- 
Julien Grall

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