On Tuesday, December 24, 2013 12:21:01 PM Roger Pau Monne wrote:
> Xen PV guests doesn't have a lapic, so disable the lapic call in mca
> initialization.
I think this is fine, but I wonder if it wouldn't be cleaner to have
lapic_enable_cmc() do the check instead. Where else do you check
lapic_d
On Tuesday, December 24, 2013 12:21:00 PM Roger Pau Monne wrote:
> Add a new event that will fire each time a PCI device is added to the
> system, and allows us to register the device with Xen.
It's really hackish to make this PCI specific. OTOH, I can't think of a
good place to have a more gener
On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote:
> Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can
> force the usage of the Xen mptable enumerator even when ACPI is
> detected.
Hmm, so I think one question is why does the existing MADT parser
not work with the
On Tuesday, December 24, 2013 12:20:59 PM Roger Pau Monne wrote:
> Also disable a couple of ACPI devices that are not usable under Dom0.
Hmm, setting debug.acpi.disabled in this way is a bit hacky. It might
be fine however if there's no way for the user to set it before booting
the kernel (as opp
On Tuesday, December 24, 2013 12:20:56 PM Roger Pau Monne wrote:
> Use madt_setup_io (from madt.c) on Xen apic_enumerator, in order to
> parse the interrupt sources from the IO APIC.
>
> I would like to get opinions, but I think we should rename and move
> madt_setup_io to io_apic.c.
It wouldn't
On 08/02/2014 21:42, John Baldwin wrote:
> On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote:
>> Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can
>> force the usage of the Xen mptable enumerator even when ACPI is
>> detected.
> Hmm, so I think one question is why d
