From: Scott Wood <scottwood@freescale.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Will Deacon <Will.Deacon@arm.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [RFC PATCH] KVM: introduce kvm_check_device
Date: Wed, 7 Jan 2015 11:45:09 -0600 [thread overview]
Message-ID: <1420652709.4961.54.camel@freescale.com> (raw)
In-Reply-To: <54AD10B1.9020709@arm.com>
On Wed, 2015-01-07 at 10:55 +0000, Andre Przywara wrote:
> Hi Scott,
>
> thanks for looking at the patch.
>
> On 06/01/15 20:52, Scott Wood wrote:
> > Out of curiosity, why do you need to test it from inside the kernel but
> > outside kvm_main.c?
>
> I need it from arch/arm/kvm/arm.c or alternatively virt/kvm/arm/vgic.c.
> The problem is that while KVM_CREATE_DEVICE works fine with checking the
> availability of the requested device, KVM_CREATE_IRQCHIP does not - and
> the latter is handled in the arch specific parts of the code. At the
> moment the GIC_V2 is the only IRQ chip, so it's all or nothing right
> now. But very soon there will be a GIC_V3, with GIC_V2 compatibility not
> always being available, so KVM_CREATE_IRQCHIP may fail although there is
> an in-kernel IRQ chip available.
> Instead of hacking something up I thought it would be cleaner to use the
> existing framework and just map KVM_CREATE_IRQCHIP to
> KVM_CREATE_DEVICE(KVM_DEV_TYPE_ARM_VGIC_V2).
In that case you'd need the full create_device functionality from
arch/arm/kvm, not just testing whether a device type is present, right?
-Scott
next prev parent reply other threads:[~2015-01-07 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 16:12 [RFC PATCH] KVM: introduce kvm_check_device Andre Przywara
2015-01-06 20:52 ` Scott Wood
2015-01-07 10:55 ` Andre Przywara
2015-01-07 17:45 ` Scott Wood [this message]
2015-01-07 18:11 ` Andre Przywara
2015-01-07 18:16 ` Scott Wood
2015-01-08 17:41 ` Andre Przywara
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=1420652709.4961.54.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Will.Deacon@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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.