From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/7] KVM: arm/arm64: Check that system supports split eoi/deactivate
Date: Fri, 6 Jan 2017 11:02:57 +0100 [thread overview]
Message-ID: <20170106100257.GD21089@cbox> (raw)
In-Reply-To: <7e44980f-d4b9-a5d0-b0a9-5424548300d8@arm.com>
On Thu, Jan 05, 2017 at 05:40:58PM +0000, Marc Zyngier wrote:
> On 10/12/16 20:47, Christoffer Dall wrote:
> > Some systems without proper firmware and/or hardware description data
> > don't support the split EOI and deactivate operation and therefore
> > don't provide an irq_set_vcpu_affinity implementation. On such
> > systems, we cannot leave the physical interrupt active after the timer
> > handler on the host has run, so we cannot support KVM with the timer
> > changes we about to introduce.
> >
> > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> > ---
> > virt/kvm/arm/arch_timer.c | 30 ++++++++++++++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> >
> > diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> > index c7c3bfd..f27a086 100644
> > --- a/virt/kvm/arm/arch_timer.c
> > +++ b/virt/kvm/arm/arch_timer.c
> > @@ -418,6 +418,31 @@ static int kvm_timer_dying_cpu(unsigned int cpu)
> > return 0;
> > }
> >
> > +static bool has_split_eoi_deactivate_support(void)
> > +{
> > + struct irq_desc *desc;
> > + struct irq_data *data;
> > + struct irq_chip *chip;
> > +
> > + /*
> > + * Check if split EOI and deactivate is supported on this machine.
> > + */
> > + desc = irq_to_desc(host_vtimer_irq);
> > + if (!desc) {
> > + kvm_err("kvm_arch_timer: no host_vtimer_irq descriptor\n");
> > + return false;
> > + }
> > +
> > + data = irq_desc_get_irq_data(desc);
> > + chip = irq_data_get_irq_chip(data);
> > + if (!chip || !chip->irq_set_vcpu_affinity) {
> > + kvm_err("kvm_arch_timer: no split EOI/deactivate; abort\n");
> > + return false;
> > + }
> > +
> > + return true;
> > +}
>
> That feels really involved. How about reporting that we don't have a
> usable VGIC altogether from the GIC driver?
>
You mean not booting the kernel at all, or establish some communication
from the GIC driver to KVM, telling KVM if it's usable for
virtualization or not?
> > +
> > int kvm_timer_hyp_init(void)
> > {
> > struct arch_timer_kvm_info *info;
> > @@ -449,6 +474,11 @@ int kvm_timer_hyp_init(void)
> > return err;
> > }
> >
> > + if (!has_split_eoi_deactivate_support()) {
> > + disable_percpu_irq(host_vtimer_irq);
> > + return -ENODEV;
> > + }
> > +
> > kvm_info("virtual timer IRQ%d\n", host_vtimer_irq);
> >
> > cpuhp_setup_state(CPUHP_AP_KVM_ARM_TIMER_STARTING,
> >
>
Thanks,
-Christoffer
next prev parent reply other threads:[~2017-01-06 10:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 20:47 [RFC PATCH 0/7] KVM: arm/arm64: Optimize arch timer register handling Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 1/7] arm64: Use physical counter for in-kernel reads Christoffer Dall
2017-01-05 18:11 ` Marc Zyngier
2017-01-06 10:00 ` Christoffer Dall
2017-01-06 10:38 ` Marc Zyngier
2017-01-06 10:53 ` Christoffer Dall
2017-01-06 15:16 ` Marc Zyngier
2017-01-09 11:29 ` Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 2/7] KVM: arm/arm64: Move kvm_vgic_flush_hwstate under disabled irq Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 3/7] KVM: arm/arm64: Support calling vgic_update_irq_pending from irq context Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 4/7] KVM: arm/arm64: Check that system supports split eoi/deactivate Christoffer Dall
2017-01-05 17:40 ` Marc Zyngier
2017-01-06 10:02 ` Christoffer Dall [this message]
2017-01-06 10:24 ` Marc Zyngier
2017-01-06 10:53 ` Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 5/7] KVM: arm/arm64: Move timer save/restore out of hyp code where possible Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 6/7] KVM: arm/arm64: Remove unnecessary timer BUG_ON operations Christoffer Dall
2016-12-10 20:47 ` [RFC PATCH 7/7] KVM: arm/arm64: Guard kvm_vgic_map_is_active against !vgic_initialized Christoffer Dall
2017-01-06 10:01 ` [RFC PATCH 0/7] KVM: arm/arm64: Optimize arch timer register handling Christoffer Dall
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=20170106100257.GD21089@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).