On Thu, 25 Feb 2016, Stefano Stabellini wrote:
> On Thu, 25 Feb 2016, Shannon Zhao wrote:
> > On 2016/2/25 18:42, Stefano Stabellini wrote:
> > > On Thu, 25 Feb 2016, Shannon Zhao wrote:
> > >> On 2016/1/28 20:56, Stefano Stabellini wrote:
> > >>> On Sat, 23 Jan 2016, Shannon Zhao wrote:
> > F
On Thu, 25 Feb 2016, Shannon Zhao wrote:
> On 2016/2/25 18:42, Stefano Stabellini wrote:
> > On Thu, 25 Feb 2016, Shannon Zhao wrote:
> >> On 2016/1/28 20:56, Stefano Stabellini wrote:
> >>> On Sat, 23 Jan 2016, Shannon Zhao wrote:
> From: Parth Dixit
>
> ACPI on Xen hypervisor uses
On 2016/2/25 18:42, Stefano Stabellini wrote:
> On Thu, 25 Feb 2016, Shannon Zhao wrote:
>> On 2016/1/28 20:56, Stefano Stabellini wrote:
>>> On Sat, 23 Jan 2016, Shannon Zhao wrote:
From: Parth Dixit
ACPI on Xen hypervisor uses MADT table for proper GIC initialization.
First
On Thu, 25 Feb 2016, Shannon Zhao wrote:
> On 2016/1/28 20:56, Stefano Stabellini wrote:
> > On Sat, 23 Jan 2016, Shannon Zhao wrote:
> >> From: Parth Dixit
> >>
> >> ACPI on Xen hypervisor uses MADT table for proper GIC initialization.
> >> First get the GIC version from GIC Distributor. Then par
On 2016/1/28 20:56, Stefano Stabellini wrote:
> On Sat, 23 Jan 2016, Shannon Zhao wrote:
>> From: Parth Dixit
>>
>> ACPI on Xen hypervisor uses MADT table for proper GIC initialization.
>> First get the GIC version from GIC Distributor. Then parse GIC related
>> subtables, collect CPU interface
On Sat, 23 Jan 2016, Shannon Zhao wrote:
> From: Parth Dixit
>
> ACPI on Xen hypervisor uses MADT table for proper GIC initialization.
> First get the GIC version from GIC Distributor. Then parse GIC related
> subtables, collect CPU interface and distributor addresses and call
> driver initializa
From: Parth Dixit
ACPI on Xen hypervisor uses MADT table for proper GIC initialization.
First get the GIC version from GIC Distributor. Then parse GIC related
subtables, collect CPU interface and distributor addresses and call
driver initialization function (which is hardware abstraction agnostic