From: Paolo Bonzini <pbonzini@redhat.com>
To: Will Deacon <will.deacon@arm.com>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Cc: Gleb Natapov <gleb@kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Alex Williamson <Alex.Williamson@redhat.com>
Subject: Re: [PATCH 1/2] KVM: device: add simple registration mechanism for kvm_device_ops
Date: Fri, 27 Jun 2014 16:17:57 +0200 [thread overview]
Message-ID: <53AD7D15.2010209@redhat.com> (raw)
In-Reply-To: <1403803817-22140-1-git-send-email-will.deacon@arm.com>
Il 26/06/2014 19:30, Will Deacon ha scritto:
> 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.
Conny, Alex (Graf & Williamson),
can you help Will here? The idea looks sane, but I'd rather merge it
with all devices converted.
Paolo
next prev parent reply other threads:[~2014-06-27 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 17:30 [PATCH 1/2] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-06-26 17:30 ` [PATCH 2/2] KVM: ARM: vgic: register kvm_device_ops dynamically Will Deacon
2014-06-27 14:17 ` Paolo Bonzini [this message]
2014-06-30 11:11 ` [PATCH 1/2] KVM: device: add simple registration mechanism for kvm_device_ops Will Deacon
2014-06-30 11:14 ` Cornelia Huck
2014-06-30 11:20 ` Will Deacon
2014-06-30 9:21 ` Cornelia Huck
2014-06-30 9:36 ` Will Deacon
2014-06-30 10:25 ` Cornelia Huck
2014-06-30 10:26 ` Will Deacon
2014-06-30 17:22 ` Paolo Bonzini
2014-06-30 17:27 ` Cornelia Huck
2014-06-30 17:31 ` Will Deacon
2014-06-30 17:32 ` Paolo Bonzini
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=53AD7D15.2010209@redhat.com \
--to=pbonzini@redhat.com \
--cc=Alex.Williamson@redhat.com \
--cc=agraf@suse.de \
--cc=christoffer.dall@linaro.org \
--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=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