[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Design doc of adding ACPI support for arm64 on Xen - version 2
- To: Julien Grall <julien.grall@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>
- From: Ian Campbell <ian.campbell@xxxxxxxxxx>
- Date: Thu, 13 Aug 2015 15:49:23 +0100
- Cc: Hangaohuai <hangaohuai@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, "Huangpeng \(Peter\)" <peter.huangpeng@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>, StefanoStabellini <stefano.stabellini@xxxxxxxxxx>, ShannonZhao <shannon.zhao@xxxxxxxxxx>, Shannon Zhao <zhaoshenglong@xxxxxxxxxx>, ParthDixit <parth.dixit@xxxxxxxxxx>, Christoffer Dall <christoffer.dall@xxxxxxxxxx>
- Delivery-date: Thu, 13 Aug 2015 15:07:02 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Thu, 2015-08-13 at 13:08 +0100, Julien Grall wrote:
>
> The MADT has to be modified in order to let DOM0 knows about his CPU
> topology. If ever need the original MADT for power management, then we
> should find a Xen specific way to do it (even if it's passing the
> orginal MADT as a backup).
Right, I was about to say something along these lines, the default set of
tables should be the ones which are expected for the guest's (including
dom0's) actual configuration and own use.
Any additional magic stuff (like host-cpufreq in dom0) already needs to do
Xen specific magic to bring itself up in a world which doesn't match that
and should request whatever real host information it needs itself, not
expect to find it in the "proper" places.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
