Re: [Xen-devel] [PATCH v2 08/41] arm/acpi : Parse FADT table and get PSCI flags

2015-07-05 Thread Parth Dixit
+shannon On 24 May 2015 at 11:35, Parth Dixit wrote: > > > On 18 May 2015 at 20:28, Julien Grall wrote: >> >> Hi Parth, >> >> On 17/05/15 21:03, Parth Dixit wrote: >> > There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, >> > the former signals to the OS that the hardware is PSCI com

Re: [Xen-devel] [PATCH v2 08/41] arm/acpi : Parse FADT table and get PSCI flags

2015-05-23 Thread Parth Dixit
On 18 May 2015 at 20:28, Julien Grall wrote: > Hi Parth, > > On 17/05/15 21:03, Parth Dixit wrote: > > There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, > > the former signals to the OS that the hardware is PSCI compliant. > > The latter selects the appropriate conduit for PSCI call

Re: [Xen-devel] [PATCH v2 08/41] arm/acpi : Parse FADT table and get PSCI flags

2015-05-18 Thread Julien Grall
Hi Parth, On 17/05/15 21:03, Parth Dixit wrote: > There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, > the former signals to the OS that the hardware is PSCI compliant. > The latter selects the appropriate conduit for PSCI calls by > toggling between Hypervisor Calls (HVC) and Secure

[Xen-devel] [PATCH v2 08/41] arm/acpi : Parse FADT table and get PSCI flags

2015-05-17 Thread Parth Dixit
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set, the former signals to the OS that the hardware is PSCI compliant. The latter selects the appropriate conduit for PSCI calls by toggling between Hypervisor Calls (HVC) and Secure Monitor Calls (SMC). FADT table contains such informatio