From: Christoffer Dall <christoffer.dall@linaro.org>
To: Will Deacon <will.deacon@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
cornelia.huck@de.ibm.com, Alex.Williamson@redhat.com,
agraf@suse.de, gleb@kernel.org, pbonzini@redhat.com,
marc.zyngier@arm.com
Subject: Re: [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops
Date: Thu, 31 Jul 2014 14:10:22 +0200 [thread overview]
Message-ID: <20140731121022.GH11610@cbox> (raw)
In-Reply-To: <1404225918-8903-1-git-send-email-will.deacon@arm.com>
On Tue, Jul 01, 2014 at 03:45:15PM +0100, Will Deacon wrote:
> kvm_ioctl_create_device currently has knowledge of all the device types
> and their associated ops. This is fairly inflexible when adding support
> for new in-kernel device emulations, so move what we currently have out
> into a table, which can support dynamic registration of ops by new
> drivers for virtual hardware.
>
> I didn't try to port all current drivers over, as it's not always clear
> which initialisation hook the ops should be registered from.
>
> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> Cc: Alex Williamson <Alex.Williamson@redhat.com>
> Cc: Alex Graf <agraf@suse.de>
> Cc: Gleb Natapov <gleb@kernel.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Will Deacon <will.deacon@arm.com>
> ---
>
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
prev parent reply other threads:[~2014-07-31 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 14:45 [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-07-01 14:45 ` [PATCH v2 2/4] KVM: ARM: vgic: register kvm_device_ops dynamically Will Deacon
2014-07-09 16:05 ` Paolo Bonzini
2014-07-09 16:13 ` Marc Zyngier
2014-07-31 12:10 ` Christoffer Dall
2014-07-31 13:25 ` Will Deacon
2014-07-01 14:45 ` [PATCH v2 3/4] KVM: s390: register flic ops dynamically Will Deacon
2014-07-01 14:45 ` [PATCH v2 4/4] KVM: VFIO: register kvm_device_ops dynamically Will Deacon
2014-07-09 16:06 ` Paolo Bonzini
2014-07-09 16:19 ` Alex Williamson
2014-07-09 16:47 ` Will Deacon
2014-07-09 16:56 ` Alex Williamson
2014-07-09 16:56 ` Alex Williamson
2014-07-02 9:17 ` [PATCH v2 1/4] KVM: device: add simple registration mechanism for kvm_device_ops Cornelia Huck
2014-07-02 9:32 ` Will Deacon
2014-07-02 10:18 ` Cornelia Huck
2014-07-31 12:10 ` Christoffer Dall [this message]
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=20140731121022.GH11610@cbox \
--to=christoffer.dall@linaro.org \
--cc=Alex.Williamson@redhat.com \
--cc=agraf@suse.de \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox