From: Shanker Donthineni <shankerd@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
kvmarm@lists.cs.columbia.edu
Cc: al.stone@linaro.org, kvm@vger.kernel.org, marc.zyngier@arm.com,
linux-kernel@vger.kernel.org, gg@slimlogic.co.uk,
linux-arm-kernel@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
fu.wei@linaro.org, Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 11 Apr 2016 10:25:33 -0500 [thread overview]
Message-ID: <570BC1ED.9080200@codeaurora.org> (raw)
In-Reply-To: <570BB461.4040704@arm.com>
Hi Julien,
On 04/11/2016 09:27 AM, Julien Grall wrote:
> Hello Hanjun,
>
> On 11/04/16 06:27, Hanjun Guo wrote:
>> On 2016/4/4 19:37, Julien Grall wrote:
>>> +static void __init gic_acpi_setup_kvm_info(void)
>>> +{
>>> + int irq;
>>> +
>>> + if (!gic_acpi_collect_virt_info()) {
>>> + pr_warn("Unable to get hardware information used for
>>> virtualization\n");
>>> + return;
>>> + }
>>> +
>>> + gic_v3_kvm_info.type = GIC_V3;
>>> +
>>> + irq = acpi_register_gsi(NULL, acpi_data.maint_irq,
>>> + acpi_data.maint_irq_mode,
>>> + ACPI_ACTIVE_HIGH);
>>> + if (irq <= 0)
>>> + return;
>>> +
>>> + gic_v3_kvm_info.maint_irq = irq;
>>> +
>>> + if (acpi_data.vcpu_base) {
>>
>> Sorry, I'm not familiar with KVM, but I got a question here, will
>> KVM works without valid vcpu_base in GICv3 mode?
>
Yes, KVM works without vcpu_base in GICv3 mode. The vcpu_base will be used
for emulatingvGICv2 feature. The vGICv3 emulation isdone through the
system registers.
> vcpu_base is only required for supporting GICv2 on GICv3.
>
Yes, you are right,
> Regards,
>
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: shankerd@codeaurora.org (Shanker Donthineni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 11 Apr 2016 10:25:33 -0500 [thread overview]
Message-ID: <570BC1ED.9080200@codeaurora.org> (raw)
In-Reply-To: <570BB461.4040704@arm.com>
Hi Julien,
On 04/11/2016 09:27 AM, Julien Grall wrote:
> Hello Hanjun,
>
> On 11/04/16 06:27, Hanjun Guo wrote:
>> On 2016/4/4 19:37, Julien Grall wrote:
>>> +static void __init gic_acpi_setup_kvm_info(void)
>>> +{
>>> + int irq;
>>> +
>>> + if (!gic_acpi_collect_virt_info()) {
>>> + pr_warn("Unable to get hardware information used for
>>> virtualization\n");
>>> + return;
>>> + }
>>> +
>>> + gic_v3_kvm_info.type = GIC_V3;
>>> +
>>> + irq = acpi_register_gsi(NULL, acpi_data.maint_irq,
>>> + acpi_data.maint_irq_mode,
>>> + ACPI_ACTIVE_HIGH);
>>> + if (irq <= 0)
>>> + return;
>>> +
>>> + gic_v3_kvm_info.maint_irq = irq;
>>> +
>>> + if (acpi_data.vcpu_base) {
>>
>> Sorry, I'm not familiar with KVM, but I got a question here, will
>> KVM works without valid vcpu_base in GICv3 mode?
>
Yes, KVM works without vcpu_base in GICv3 mode. The vcpu_base will be used
for emulatingvGICv2 feature. The vGICv3 emulation isdone through the
system registers.
> vcpu_base is only required for supporting GICv2 on GICv3.
>
Yes, you are right,
> Regards,
>
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Shanker Donthineni <shankerd@codeaurora.org>
To: Julien Grall <julien.grall@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
kvmarm@lists.cs.columbia.edu
Cc: al.stone@linaro.org, kvm@vger.kernel.org, marc.zyngier@arm.com,
linux-kernel@vger.kernel.org, fu.wei@linaro.org,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
linux-arm-kernel@lists.infradead.org, gg@slimlogic.co.uk
Subject: Re: [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information
Date: Mon, 11 Apr 2016 10:25:33 -0500 [thread overview]
Message-ID: <570BC1ED.9080200@codeaurora.org> (raw)
In-Reply-To: <570BB461.4040704@arm.com>
Hi Julien,
On 04/11/2016 09:27 AM, Julien Grall wrote:
> Hello Hanjun,
>
> On 11/04/16 06:27, Hanjun Guo wrote:
>> On 2016/4/4 19:37, Julien Grall wrote:
>>> +static void __init gic_acpi_setup_kvm_info(void)
>>> +{
>>> + int irq;
>>> +
>>> + if (!gic_acpi_collect_virt_info()) {
>>> + pr_warn("Unable to get hardware information used for
>>> virtualization\n");
>>> + return;
>>> + }
>>> +
>>> + gic_v3_kvm_info.type = GIC_V3;
>>> +
>>> + irq = acpi_register_gsi(NULL, acpi_data.maint_irq,
>>> + acpi_data.maint_irq_mode,
>>> + ACPI_ACTIVE_HIGH);
>>> + if (irq <= 0)
>>> + return;
>>> +
>>> + gic_v3_kvm_info.maint_irq = irq;
>>> +
>>> + if (acpi_data.vcpu_base) {
>>
>> Sorry, I'm not familiar with KVM, but I got a question here, will
>> KVM works without valid vcpu_base in GICv3 mode?
>
Yes, KVM works without vcpu_base in GICv3 mode. The vcpu_base will be used
for emulatingvGICv2 feature. The vGICv3 emulation isdone through the
system registers.
> vcpu_base is only required for supporting GICv2 on GICv3.
>
Yes, you are right,
> Regards,
>
--
Shanker Donthineni
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-04-11 15:24 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 11:37 [PATCH v5 0/9] arm64: Add support for KVM with ACPI Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` [PATCH v5 1/9] clocksource: arm_arch_timer: Gather KVM specific information in a structure Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-04 11:37 ` [PATCH v5 2/9] clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-04 11:37 ` [PATCH v5 3/9] irqchip/gic-v2: Gather ACPI specific data in a single structure Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-11 2:47 ` Hanjun Guo
2016-04-11 2:47 ` Hanjun Guo
2016-04-11 2:47 ` Hanjun Guo
2016-04-04 11:37 ` [PATCH v5 4/9] irqchip/gic-v2: Parse and export virtual GIC information Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:04 ` Christoffer Dall
2016-04-06 17:04 ` Christoffer Dall
2016-04-06 17:04 ` Christoffer Dall
2016-04-06 17:40 ` Julien Grall
2016-04-06 17:40 ` Julien Grall
2016-04-06 17:40 ` Julien Grall
2016-04-11 3:17 ` Hanjun Guo
2016-04-11 3:17 ` Hanjun Guo
2016-04-11 3:17 ` Hanjun Guo
2016-04-11 13:54 ` Julien Grall
2016-04-11 13:54 ` Julien Grall
2016-04-11 13:54 ` Julien Grall
2016-04-04 11:37 ` [PATCH v5 5/9] irqchip/gic-v3: Gather all ACPI specific data in a single structure Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-06 17:26 ` Christoffer Dall
2016-04-11 5:21 ` Hanjun Guo
2016-04-11 5:21 ` Hanjun Guo
2016-04-11 5:21 ` Hanjun Guo
2016-04-04 11:37 ` [PATCH v5 6/9] irqchip/gic-v3: Parse and export virtual GIC information Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:22 ` Christoffer Dall
2016-04-06 17:22 ` Christoffer Dall
2016-04-06 17:22 ` Christoffer Dall
2016-04-06 17:45 ` Julien Grall
2016-04-06 17:45 ` Julien Grall
2016-04-06 17:45 ` Julien Grall
2016-04-09 2:29 ` Shanker Donthineni
2016-04-09 2:29 ` Shanker Donthineni
2016-04-09 2:29 ` Shanker Donthineni
2016-04-11 14:03 ` Julien Grall
2016-04-11 14:03 ` Julien Grall
2016-04-11 14:03 ` Julien Grall
2016-04-11 5:27 ` Hanjun Guo
2016-04-11 5:27 ` Hanjun Guo
2016-04-11 5:27 ` Hanjun Guo
2016-04-11 14:27 ` Julien Grall
2016-04-11 14:27 ` Julien Grall
2016-04-11 14:27 ` Julien Grall
2016-04-11 15:25 ` Shanker Donthineni [this message]
2016-04-11 15:25 ` Shanker Donthineni
2016-04-11 15:25 ` Shanker Donthineni
2016-04-13 10:11 ` Hanjun Guo
2016-04-13 10:11 ` Hanjun Guo
2016-04-13 10:11 ` Hanjun Guo
2016-04-04 11:37 ` [PATCH v5 7/9] KVM: arm/arm64: arch_timer: Rely on the arch timer to parse the firmware tables Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` [PATCH v5 8/9] KVM: arm/arm64: vgic: Rely on the GIC driver " Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:25 ` Christoffer Dall
2016-04-06 17:25 ` Christoffer Dall
2016-04-06 17:25 ` Christoffer Dall
2016-04-04 11:37 ` [PATCH v5 9/9] clocksource: arm_arch_timer: Remove arch_timer_get_timecounter Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-04 11:37 ` Julien Grall
2016-04-06 17:28 ` [PATCH v5 0/9] arm64: Add support for KVM with ACPI Christoffer Dall
2016-04-06 17:28 ` Christoffer Dall
2016-04-06 17:28 ` Christoffer Dall
2016-04-06 17:49 ` Julien Grall
2016-04-06 17:49 ` Julien Grall
2016-04-06 17:49 ` Julien Grall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570BC1ED.9080200@codeaurora.org \
--to=shankerd@codeaurora.org \
--cc=al.stone@linaro.org \
--cc=fu.wei@linaro.org \
--cc=gg@slimlogic.co.uk \
--cc=hanjun.guo@linaro.org \
--cc=jason@lakedaemon.net \
--cc=julien.grall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.