From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
avi@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com,
markmc@redhat.com
Subject: Re: [PATCHv3 3/4] kvm: convert bus to slots_lock
Date: Mon, 29 Jun 2009 14:04:18 -0300 [thread overview]
Message-ID: <20090629170418.GA17937@amt.cnet> (raw)
In-Reply-To: <20090629163851.GD22029@redhat.com>
On Mon, Jun 29, 2009 at 07:38:51PM +0300, Michael S. Tsirkin wrote:
> On Mon, Jun 29, 2009 at 12:50:31PM -0300, Marcelo Tosatti wrote:
> > > diff --git a/arch/x86/kvm/i8259.c b/arch/x86/kvm/i8259.c
> > > index 148c52a..1851aec 100644
> > > --- a/arch/x86/kvm/i8259.c
> > > +++ b/arch/x86/kvm/i8259.c
> > > @@ -548,6 +548,6 @@ struct kvm_pic *kvm_create_pic(struct kvm *kvm)
> > > * Initialize PIO device
> > > */
> > > kvm_iodevice_init(&s->dev, &picdev_ops);
> > > - kvm_io_bus_register_dev(&kvm->pio_bus, &s->dev);
> > > + kvm_io_bus_register_dev(kvm, &kvm->pio_bus, &s->dev);
> > > return s;
> >
> > case KVM_CREATE_PIT2:
> > create_pit:
> > mutex_lock(&kvm->lock);
> > kvm_io_bus_register_dev
> > down_write(slots_lock);
> >
> > But the order is slots_lock -> kvm->lock.
> >
> > (you might want to update the comment on top of kvm_main.c to
> > reflect that).
>
> Good catch. I think it's easiest to replace kvm->lock by slots_lock
> here as well. Does something like the following make sense?
> If yes I'll roll it up in the series.
Looks good. Also please update the comment on top of kvm_main.c.
next prev parent reply other threads:[~2009-06-29 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1246276816.git.mst@redhat.com>
2009-06-29 12:08 ` [PATCHv3 1/4] kvm: document locking for kvm_io_device_ops Michael S. Tsirkin
2009-06-29 12:09 ` [PATCHv3 2/4] kvm: switch coalesced mmio changes to slots_lock Michael S. Tsirkin
2009-06-29 12:09 ` [PATCHv3 3/4] kvm: convert bus " Michael S. Tsirkin
2009-06-29 15:50 ` Marcelo Tosatti
2009-06-29 16:38 ` Michael S. Tsirkin
2009-06-29 17:04 ` Marcelo Tosatti [this message]
2009-06-29 12:09 ` [PATCHv3 4/4] kvm: remove in_range from io devices Michael S. Tsirkin
2009-06-29 12:20 ` Michael S. Tsirkin
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=20090629170418.GA17937@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.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 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.