From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH v3] IO: Intelligent device lookup on bus
Date: Wed, 27 Jul 2011 15:37:30 +0300 [thread overview]
Message-ID: <4E30068A.8010905@redhat.com> (raw)
In-Reply-To: <1311768097.19123.11.camel@lappy>
On 07/27/2011 03:01 PM, Sasha Levin wrote:
> > >
> > > -static inline struct kvm_pic *to_pic(struct kvm_io_device *dev)
> > > +static inline struct kvm_pic *to_pic(struct kvm_io_device *dev, gpa_t addr)
> > > {
> > > - return container_of(dev, struct kvm_pic, dev);
> > > + switch (addr) {
> > > + case 0x20:
> > > + case 0x21:
> > > + return container_of(dev, struct kvm_pic, dev_master);
> > > + case 0xa0:
> > > + case 0xa1:
> > > + return container_of(dev, struct kvm_pic, dev_slave);
> > > + case 0x4d0:
> > > + case 0x4d1:
> > > + return container_of(dev, struct kvm_pic, dev_eclr);
> > > + }
> > > +
> > > + return NULL;
> > > }
> >
> > Somewhat ugly. I think
> >
> > int picdev_write_master(...)
> > {
> > return pcidev_write(container_of(...), ...);
> > }
> >
> > is nicer, no?
>
> It would mean we need a total of 6 wrappers for master, slave and eclr
> instead of this switch, if that sounds ok I'll change it.
IMO, they're better than the switch.
> >
> >
> > > if (ret< 0)
> > > goto out_free_dev;
> > > list_add_tail(&dev->list,&kvm->coalesced_zones);
> > > diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
> > > index 73358d2..f59c1e8 100644
> > > --- a/virt/kvm/eventfd.c
> > > +++ b/virt/kvm/eventfd.c
> > > @@ -586,7 +586,8 @@ kvm_assign_ioeventfd(struct kvm *kvm, struct kvm_ioeventfd *args)
> > >
> > > kvm_iodevice_init(&p->dev,&ioeventfd_ops);
> > >
> > > - ret = kvm_io_bus_register_dev(kvm, bus_idx,&p->dev);
> > > + ret = kvm_io_bus_register_dev(kvm, bus_idx, p->addr, p->length,
> > > + &p->dev);
> >
> > Should this be p->length or 1?
>
> We register p->length since when we process a write, the operation
> should be fully contained within the IO space of the device.
>
> We verify that the write happens on the first byte within ioeventfd
> write handler.
Ok.
> >
> > > #include<asm/processor.h>
> > > #include<asm/io.h>
> > > @@ -2391,24 +2393,94 @@ static void kvm_io_bus_destroy(struct kvm_io_bus *bus)
> > > int i;
> > >
> > > for (i = 0; i< bus->dev_count; i++) {
> > > - struct kvm_io_device *pos = bus->devs[i];
> > > + struct kvm_io_device *pos = bus->range[i].dev;
> > >
> >
> > This will call the destructor three times for the PIC. Is this safe?
>
> PIC doesn't have a destructor for devices, the code above just does
> nothing for PIC devices.
Ok.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-07-27 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 6:15 [PATCH v3] IO: Intelligent device lookup on bus Sasha Levin
2011-07-27 11:35 ` Avi Kivity
2011-07-27 12:01 ` Sasha Levin
2011-07-27 12:37 ` Avi Kivity [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=4E30068A.8010905@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mtosatti@redhat.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