[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC PATCH v2 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall
- To: "Dario Faggioli" <dario.faggioli@xxxxxxxxxx>
- From: "Jan Beulich" <JBeulich@xxxxxxxx>
- Date: Thu, 13 Mar 2014 17:04:31 +0000
- Cc: paolo.valente@xxxxxxxxxx, Keir Fraser <keir@xxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, stefano.stabellini@xxxxxxxxxxxxx, Tim Deegan <tim@xxxxxxx>, Ian.Jackson@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxx, julien.grall@xxxxxxxxxx, etrudeau@xxxxxxxxxxxx, Arianna Avanzini <avanzini.arianna@xxxxxxxxx>, viktor.kleinik@xxxxxxxxxxxxxxx
- Delivery-date: Thu, 13 Mar 2014 17:04:40 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
>>> On 13.03.14 at 17:53, Dario Faggioli <dario.faggioli@xxxxxxxxxx> wrote:
> Do you happen to see any alternative solution, in absence of proper
> DT/ACPI support in the guest OS? If no, what would be the best solution
> to keep this out of x86 way? Is #ifdef, as Ian's suggesting, fine?
Yes, but I'd strongly suggest using a white list approach rather than
a blacklist one here (which of course only matters if there'll ever be
a port to another architecture).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
