From: Julien Grall <julien.grall@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com,
fu.wei@linaro.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, wei@redhat.com,
al.stone@linaro.org, gg@slimlogic.co.uk,
daniel.lezcano@linaro.org
Subject: Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI
Date: Wed, 6 Apr 2016 18:49:58 +0100 [thread overview]
Message-ID: <57054C46.1080800@arm.com> (raw)
In-Reply-To: <20160406172805.GJ8961@cbox>
Hi Christoffer,
On 06/04/2016 18:28, Christoffer Dall wrote:
> On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote:
>> Hello,
>>
>> This patch series allows KVM to work with ACPI on ARM64.
>>
>> Currently, the firmware tables are parsed by the the virtual timer and virtual
>> GIC code in order to configure them correctly.
>>
>> However the parsing of these tables is already done in the GIC and arch timer
>> drivers. This patch series introduces new helpers to retrieve the information
>> from the different drivers in order to avoid duplication of the parsing code.
>>
>> To make the merge easier via the different trees, each patch modifies a single
>> subsystem. The suggested plan to merge the series is divided in 3 steps:
>>
>> 1) Patches #1-#2 are merged via the clocksource tree
>> Patches #2-#6 are merged via the irqchip tree
>> 2) Patches #7-#8 are merge via the KVM tree
>> 3) Patch #9 is merged via the clocksource tree.
>>
>
> I'm not a clocksource or irqchip expert, and far from an ACPI expert,
> but this series overall looks good to me now.
>
> I guess we'll need to wait until the patches are in the clocksource and
> irqchip trees, and then merge that into the kvmarm tree, and apply patch
> 7 and 8 on top, or is there a simpler way to do this?
The simpler way would be carrying all the patches in a single tree (such
as the KVM ARM tree). If we are going this way, I would need the ack
from all the maintainers in this case.
Regards,
--
Julien Grall
WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: al.stone@linaro.org, kvm@vger.kernel.org, marc.zyngier@arm.com,
daniel.lezcano@linaro.org, linux-kernel@vger.kernel.org,
fu.wei@linaro.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, gg@slimlogic.co.uk
Subject: Re: [PATCH v5 0/9] arm64: Add support for KVM with ACPI
Date: Wed, 6 Apr 2016 18:49:58 +0100 [thread overview]
Message-ID: <57054C46.1080800@arm.com> (raw)
In-Reply-To: <20160406172805.GJ8961@cbox>
Hi Christoffer,
On 06/04/2016 18:28, Christoffer Dall wrote:
> On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote:
>> Hello,
>>
>> This patch series allows KVM to work with ACPI on ARM64.
>>
>> Currently, the firmware tables are parsed by the the virtual timer and virtual
>> GIC code in order to configure them correctly.
>>
>> However the parsing of these tables is already done in the GIC and arch timer
>> drivers. This patch series introduces new helpers to retrieve the information
>> from the different drivers in order to avoid duplication of the parsing code.
>>
>> To make the merge easier via the different trees, each patch modifies a single
>> subsystem. The suggested plan to merge the series is divided in 3 steps:
>>
>> 1) Patches #1-#2 are merged via the clocksource tree
>> Patches #2-#6 are merged via the irqchip tree
>> 2) Patches #7-#8 are merge via the KVM tree
>> 3) Patch #9 is merged via the clocksource tree.
>>
>
> I'm not a clocksource or irqchip expert, and far from an ACPI expert,
> but this series overall looks good to me now.
>
> I guess we'll need to wait until the patches are in the clocksource and
> irqchip trees, and then merge that into the kvmarm tree, and apply patch
> 7 and 8 on top, or is there a simpler way to do this?
The simpler way would be carrying all the patches in a single tree (such
as the KVM ARM tree). If we are going this way, I would need the ack
from all the maintainers in this case.
Regards,
--
Julien Grall
WARNING: multiple messages have this Message-ID (diff)
From: julien.grall@arm.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/9] arm64: Add support for KVM with ACPI
Date: Wed, 6 Apr 2016 18:49:58 +0100 [thread overview]
Message-ID: <57054C46.1080800@arm.com> (raw)
In-Reply-To: <20160406172805.GJ8961@cbox>
Hi Christoffer,
On 06/04/2016 18:28, Christoffer Dall wrote:
> On Mon, Apr 04, 2016 at 12:37:31PM +0100, Julien Grall wrote:
>> Hello,
>>
>> This patch series allows KVM to work with ACPI on ARM64.
>>
>> Currently, the firmware tables are parsed by the the virtual timer and virtual
>> GIC code in order to configure them correctly.
>>
>> However the parsing of these tables is already done in the GIC and arch timer
>> drivers. This patch series introduces new helpers to retrieve the information
>> from the different drivers in order to avoid duplication of the parsing code.
>>
>> To make the merge easier via the different trees, each patch modifies a single
>> subsystem. The suggested plan to merge the series is divided in 3 steps:
>>
>> 1) Patches #1-#2 are merged via the clocksource tree
>> Patches #2-#6 are merged via the irqchip tree
>> 2) Patches #7-#8 are merge via the KVM tree
>> 3) Patch #9 is merged via the clocksource tree.
>>
>
> I'm not a clocksource or irqchip expert, and far from an ACPI expert,
> but this series overall looks good to me now.
>
> I guess we'll need to wait until the patches are in the clocksource and
> irqchip trees, and then merge that into the kvmarm tree, and apply patch
> 7 and 8 on top, or is there a simpler way to do this?
The simpler way would be carrying all the patches in a single tree (such
as the KVM ARM tree). If we are going this way, I would need the ack
from all the maintainers in this case.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2016-04-06 17:50 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
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 [this message]
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=57054C46.1080800@arm.com \
--to=julien.grall@arm.com \
--cc=al.stone@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=fu.wei@linaro.org \
--cc=gg@slimlogic.co.uk \
--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=wei@redhat.com \
/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.