From: Marcel Apfelbaum <marcel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, cornelia.huck@de.ibm.com,
Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH V3] hw/virtio-pci: fix virtio behaviour
Date: Fri, 22 Jul 2016 10:55:10 +0300 [thread overview]
Message-ID: <5791D15E.40302@redhat.com> (raw)
In-Reply-To: <20160722012006-mutt-send-email-mst@kernel.org>
On 07/22/2016 01:21 AM, Michael S. Tsirkin wrote:
> On Thu, Jul 21, 2016 at 11:58:52PM +0200, Gerd Hoffmann wrote:
>> Hi,
>>
>>> Actually this can still break existing scripts:
>>> stick a device on express bus but add disable-modern=on
>>> Gave you a legacy device previously but it no longer does.
>>
>> Unlikely to happen in practice because there is little reason to use
>> disable-modern=on in 2.6 & older because that is the default ...
>
> Good point, I forgot.
>
>> Still we can default to legacy=yes in case disable-modern=on +
>> disable-legacy=auto.
>
> Given the above I'm not sure it's worth it. I'll leave it to Marcel
> to decide.
Hi Michael,Gerd,
I think it doesn't worth to make the code more complicated
for an uninteresting scenario.
>
>> And throw and error in case both modern and legacy
>> are explicitly disabled (as already suggested elsewhere in this thread).
>>
There is already a patch for this upstream:
https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg05263.html
Michael, since the rc1 is approaching fast, can you please advice
on what changes to make to the commit message and if you prefer me
to add the Greg patch to the series and re-send, or you can take it separately?
Thanks,
Marcel
>> cheers,
>> Gerd
prev parent reply other threads:[~2016-07-22 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 15:28 [Qemu-devel] [PATCH V3] hw/virtio-pci: fix virtio behaviour Marcel Apfelbaum
2016-07-21 5:43 ` Marcel Apfelbaum
2016-07-21 6:35 ` Gerd Hoffmann
2016-07-21 8:54 ` Cornelia Huck
2016-07-21 9:26 ` Marcel Apfelbaum
2016-07-21 11:03 ` Cornelia Huck
2016-07-21 20:18 ` Michael S. Tsirkin
2016-07-22 7:44 ` Marcel Apfelbaum
2016-07-21 21:37 ` Michael S. Tsirkin
2016-07-21 21:58 ` Gerd Hoffmann
2016-07-21 22:21 ` Michael S. Tsirkin
2016-07-22 7:55 ` Marcel Apfelbaum [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=5791D15E.40302@redhat.com \
--to=marcel@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).