Hi Christoffer,
On 09/02/16 20:49, Christoffer Dall wrote:
+static void __init gic_acpi_setup_kvm_info(void)
+{
+ gic_v2_kvm_info.type = GIC_V2;
+
+ gic_v2_kvm_info.maint_irq = acpi_register_gsi(NULL,
+ acpi_data.maint_irq,
+
On 10/02/16 14:19, Julien Grall wrote:
> Hi Christoffer,
>
> On 09/02/16 20:49, Christoffer Dall wrote:
>>> +static void __init gic_acpi_setup_kvm_info(void)
>>> +{
>>> + gic_v2_kvm_info.type = GIC_V2;
>>> +
>>> + gic_v2_kvm_info.maint_irq = acpi_register_gsi(NULL,
>>> +
Hi Marc,
On 10/02/16 14:46, Marc Zyngier wrote:
On 10/02/16 14:19, Julien Grall wrote:
On 09/02/16 20:49, Christoffer Dall wrote:
+static void __init gic_acpi_setup_kvm_info(void)
+{
+ gic_v2_kvm_info.type = GIC_V2;
+
+ gic_v2_kvm_info.maint_irq = acpi_register_gsi(NULL,
+
On Mon, Feb 08, 2016 at 04:47:27PM +, Julien Grall wrote:
> For now, the firmware tables are parsed 2 times: once in the GIC
> drivers, the other timer when initializing the vGIC. It means code
> duplication and make more tedious to add the support for another
> firmware table (like ACPI).
>
On 02/09/2016 02:49 PM, Christoffer Dall wrote:
> On Mon, Feb 08, 2016 at 04:47:27PM +, Julien Grall wrote:
>> For now, the firmware tables are parsed 2 times: once in the GIC
>> drivers, the other timer when initializing the vGIC. It means code
>> duplication and make more tedious to add
Julien,
On 08/02/16 16:47, Julien Grall wrote:
> For now, the firmware tables are parsed 2 times: once in the GIC
> drivers, the other timer when initializing the vGIC. It means code
> duplication and make more tedious to add the support for another
> firmware table (like ACPI).
>
> Introduce a
