From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Shirley Ma <mashirle@us.ibm.com>,
Jamie Lokier <jamie@shareable.org>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Amit Shah <amit.shah@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
hch@lst.de
Subject: Re: [PULL] virtio
Date: Sun, 7 Mar 2010 13:04:57 +0200 [thread overview]
Message-ID: <20100307110457.GB20004@redhat.com> (raw)
In-Reply-To: <40B76F19-1E35-4956-A34E-0A83A403F97D@suse.de>
On Sun, Mar 07, 2010 at 11:57:23AM +0100, Alexander Graf wrote:
>
> On 07.03.2010, at 11:42, Michael S. Tsirkin wrote:
>
> > Linus,
> > Please pull another virtio fix: this one fixes hotplug and
> > was supposed to be applied by Rusty already
> > (http://lkml.org/lkml/2009/11/30/451), but apparently got lost,
> > somehow.
> >
> > Thanks!
> >
> > The following changes since commit 3119815912a220bdac943dfbdfee640414c0c611:
> > Michael S. Tsirkin (1):
> > virtio: fix out of range array access
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git for-linus
> >
> > Michael S. Tsirkin (1):
> > virtio: set pci bus master enable bit
>
> This is still missing an identifier for the hypervisor. We need to know if the guest will ever set bus master enabled or not, so we can have a compat hack in qemu to not check for it.
>
>
> Alex
This patch fixes hotplug with qemu 0.11-0.12 which can't make use of a new
identifier without a time machine.
IMHO we can't add new identifiers in time for 2.6.34 anyway, so if you
want to do that, please send a patch and have it queued up for the next
release. But I don't think we need an identifier for compat hack.
Hypervisor can detect buggy guests when they set status to OK without
enabling bus master first.
Makes sense?
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Adam Litke <agl@us.ibm.com>, Amit Shah <amit.shah@redhat.com>,
hch@lst.de, Jamie Lokier <jamie@shareable.org>,
Shirley Ma <mashirle@us.ibm.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>
Subject: Re: [PULL] virtio
Date: Sun, 7 Mar 2010 13:04:57 +0200 [thread overview]
Message-ID: <20100307110457.GB20004@redhat.com> (raw)
In-Reply-To: <40B76F19-1E35-4956-A34E-0A83A403F97D@suse.de>
On Sun, Mar 07, 2010 at 11:57:23AM +0100, Alexander Graf wrote:
>
> On 07.03.2010, at 11:42, Michael S. Tsirkin wrote:
>
> > Linus,
> > Please pull another virtio fix: this one fixes hotplug and
> > was supposed to be applied by Rusty already
> > (http://lkml.org/lkml/2009/11/30/451), but apparently got lost,
> > somehow.
> >
> > Thanks!
> >
> > The following changes since commit 3119815912a220bdac943dfbdfee640414c0c611:
> > Michael S. Tsirkin (1):
> > virtio: fix out of range array access
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git for-linus
> >
> > Michael S. Tsirkin (1):
> > virtio: set pci bus master enable bit
>
> This is still missing an identifier for the hypervisor. We need to know if the guest will ever set bus master enabled or not, so we can have a compat hack in qemu to not check for it.
>
>
> Alex
This patch fixes hotplug with qemu 0.11-0.12 which can't make use of a new
identifier without a time machine.
IMHO we can't add new identifiers in time for 2.6.34 anyway, so if you
want to do that, please send a patch and have it queued up for the next
release. But I don't think we need an identifier for compat hack.
Hypervisor can detect buggy guests when they set status to OK without
enabling bus master first.
Makes sense?
--
MST
next prev parent reply other threads:[~2010-03-07 11:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 10:42 [PULL] virtio Michael S. Tsirkin
2010-03-07 10:42 ` Michael S. Tsirkin
2010-03-07 10:57 ` Alexander Graf
2010-03-07 11:04 ` Michael S. Tsirkin [this message]
2010-03-07 11:04 ` Michael S. Tsirkin
2010-03-07 11:11 ` Alexander Graf
2010-03-07 11:11 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2013-02-26 5:33 Rusty Russell
2012-10-05 1:39 Rusty Russell
2012-10-05 1:39 ` Rusty Russell
2012-07-30 4:03 Rusty Russell
2012-05-22 2:51 Rusty Russell
2012-05-22 3:24 ` Linus Torvalds
2012-05-22 4:29 ` Rusty Russell
[not found] <87wrbkvh3v.fsf@rustcorp.com.au>
2011-11-01 11:45 ` Michael S. Tsirkin
2011-11-01 11:45 ` Michael S. Tsirkin
2011-11-01 12:33 ` Sasha Levin
2011-11-01 12:33 ` Sasha Levin
2011-11-01 12:42 ` Michael S. Tsirkin
2011-11-01 12:42 ` Michael S. Tsirkin
2011-11-01 12:45 ` Sasha Levin
2011-11-01 12:45 ` Sasha Levin
2011-11-02 1:09 ` Rusty Russell
2011-11-02 1:09 ` Rusty Russell
2011-11-02 4:52 ` Sasha Levin
2011-11-02 4:52 ` Sasha Levin
2011-11-02 22:07 ` Rusty Russell
2011-11-02 22:07 ` Rusty Russell
2010-08-05 3:37 Rusty Russell
2010-05-19 12:53 Rusty Russell
2010-05-19 12:53 Rusty Russell
2010-03-22 14:34 Michael S. Tsirkin
2010-03-22 14:34 Michael S. Tsirkin
2010-02-28 18:43 Michael S. Tsirkin
2010-02-28 18:43 Michael S. Tsirkin
2009-06-12 12:48 Rusty Russell
2009-06-12 12:48 Rusty Russell
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=20100307110457.GB20004@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@linux.vnet.ibm.com \
--cc=amit.shah@redhat.com \
--cc=hch@lst.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashirle@us.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.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 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.