From: Chris Wright <chrisw@sous-sol.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: avi@redhat.com, chrisw@sous-sol.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [KVM PATCH v2 2/3] kvm: cleanup io_device code
Date: Wed, 27 May 2009 22:49:04 -0700 [thread overview]
Message-ID: <20090528054904.GK20823@sequoia.sous-sol.org> (raw)
In-Reply-To: <20090527213744.24324.82745.stgit@dev.haskins.net>
* Gregory Haskins (ghaskins@novell.com) wrote:
> We modernize the io_device code so that we use container_of() instead of
> dev->private, and move the vtable to a separate ops structure
> (theoretically allows better caching for multiple instances of the same
> ops structure)
Looks like a nice cleanup. Couple minor nits.
> +static struct kvm_io_device_ops pit_dev_ops = {
> + .read = pit_ioport_read,
> + .write = pit_ioport_write,
> + .in_range = pit_in_range,
> +};
> +
> +static struct kvm_io_device_ops speaker_dev_ops = {
> + .read = speaker_ioport_read,
> + .write = speaker_ioport_write,
> + .in_range = speaker_in_range,
> +};
kvm_io_device_ops instances could be made const.
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -2227,7 +2227,7 @@ static struct kvm_io_device *vcpu_find_pervcpu_dev(struct kvm_vcpu *vcpu,
>
> if (vcpu->arch.apic) {
> dev = &vcpu->arch.apic->dev;
> - if (dev->in_range(dev, addr, len, is_write))
> + if (dev->ops->in_range(dev, addr, len, is_write))
> return dev;
> --- a/virt/kvm/iodev.h
> +++ b/virt/kvm/iodev.h
> @@ -18,7 +18,9 @@
>
> #include <linux/kvm_types.h>
>
> -struct kvm_io_device {
> +struct kvm_io_device;
> +
> +struct kvm_io_device_ops {
> void (*read)(struct kvm_io_device *this,
> gpa_t addr,
> int len,
> @@ -30,16 +32,25 @@ struct kvm_io_device {
> int (*in_range)(struct kvm_io_device *this, gpa_t addr, int len,
> int is_write);
> void (*destructor)(struct kvm_io_device *this);
> +};
> +
>
> - void *private;
> +struct kvm_io_device {
> + struct kvm_io_device_ops *ops;
> };
Did you plan to extend kvm_io_device struct?
> +static inline void kvm_iodevice_init(struct kvm_io_device *dev,
> + struct kvm_io_device_ops *ops)
> +{
> + dev->ops = ops;
> +}
And similarly, did you have a plan to do more with kvm_iodevice_init()?
Otherwise looking a bit like overkill to me.
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -2456,7 +2456,7 @@ struct kvm_io_device *kvm_io_bus_find_dev(struct kvm_io_bus *bus,
> for (i = 0; i < bus->dev_count; i++) {
> struct kvm_io_device *pos = bus->devs[i];
>
> - if (pos->in_range(pos, addr, len, is_write))
> + if (kvm_iodevice_inrange(pos, addr, len, is_write))
> return pos;
> }
You converted this to the helper but not vcpu_find_pervcpu_dev() (not
convinced it actually helps readability, but consistency is good). BTW,
while there, s/kvm_iodevice_inrange/kvm_iodevice_in_range/ would be nice.
thanks,
-chris
next prev parent reply other threads:[~2009-05-28 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 21:37 [KVM PATCH v2 0/3] mmio/pio cleanup Gregory Haskins
2009-05-27 21:37 ` [KVM PATCH v2 1/3] kvm: fix potential coalesced_mmio leak on shutdown Gregory Haskins
2009-05-27 21:37 ` [KVM PATCH v2 2/3] kvm: cleanup io_device code Gregory Haskins
2009-05-28 5:49 ` Chris Wright [this message]
2009-05-28 11:59 ` Gregory Haskins
2009-05-27 21:37 ` [KVM PATCH v2 3/3] kvm: do not register i8254 PIO regions until we are initialized Gregory Haskins
2009-05-31 10:14 ` [KVM PATCH v2 0/3] mmio/pio cleanup Avi Kivity
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=20090528054904.GK20823@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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