All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, cornelia.huck@de.ibm.com,
	marcel@redhat.com, vkaplans@redhat.com
Subject: Re: [Qemu-devel] [RFC] virtio-bus: Plug devices after features are negotiated
Date: Fri, 9 Sep 2016 18:16:27 +0200	[thread overview]
Message-ID: <bcf8e621-1437-2442-6529-4c0c843e325b@redhat.com> (raw)
In-Reply-To: <20160909183927-mutt-send-email-mst@kernel.org>



On 09/09/2016 05:39 PM, Michael S. Tsirkin wrote:
> On Fri, Sep 09, 2016 at 04:14:59PM +0200, Maxime Coquelin wrote:
>> > Currently, devices are plugged before features are negotiated.
>> > If the backend doesn't support VIRTIO_F_VERSION_1, the transport
>> > need to rewind some settings.
>> >
>> > This is the case for both PCI and CCW.
>> > For CCW, a post_plugged callback had been introduced, where
>> > max_rev field is just updated if VIRTIO_F_VERSION_1 is not
>> > supported by the backend.
>> > For PCI, implementing the post_plugged would be much more
>> > complicated, so the current fix consists in checking whether
>> > the backend supports VIRTIO_F_VERSION_1 in the backend.
>> >
>> > This patch propose to replace existing solutions with a common
>> > approach by negociating features before ->device_plugged() is
>> > called. A pre_plugged callback is introduced so that the
>> > transports can set their supported features.
>> >
>> > Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
>> > Cc: Marcel Apfelbaum <marcel@redhat.com>
>> > Cc: Michael S. Tsirkin <mst@redhat.com>
>> > Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
> Looks good - can you pls test and post a non-RFC?
>

Do you mean having this also in stable, or keeping
it based on top of former pci-only patch?

I already tested it for PCI, but cannot test it for CCW.

Thanks,
Maxime

  reply	other threads:[~2016-09-09 16:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 10:14 [Qemu-devel] [PATCH 0/2] virtio-pci: Improve device plugging whith legacy backends Maxime Coquelin
2016-09-09 10:14 ` [Qemu-devel] [PATCH 1/2] virtio: Add backend feature testing functionnality Maxime Coquelin
2016-09-09 10:33   ` Cornelia Huck
2016-09-09 10:48     ` Marcel Apfelbaum
2016-09-09 10:55       ` Cornelia Huck
2016-09-09 11:02         ` Marcel Apfelbaum
2016-09-09 11:20           ` Cornelia Huck
2016-09-09 11:36             ` Maxime Coquelin
2016-09-09 11:47               ` Marcel Apfelbaum
2016-09-09 10:14 ` [Qemu-devel] [PATCH 2/2] virtio-pci: Disable modern interface if backend without VIRTIO_F_VERSION_1 Maxime Coquelin
2016-09-09 10:40   ` Cornelia Huck
2016-09-09 11:04     ` Marcel Apfelbaum
2016-09-09 11:20       ` Cornelia Huck
2016-09-09 11:44         ` Maxime Coquelin
2016-09-09 11:49           ` Cornelia Huck
2016-09-09 12:01             ` Maxime Coquelin
2016-09-09 14:14             ` [Qemu-devel] [RFC] virtio-bus: Plug devices after features are negotiated Maxime Coquelin
2016-09-09 15:39               ` Michael S. Tsirkin
2016-09-09 16:16                 ` Maxime Coquelin [this message]
2016-09-09 18:44                   ` 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=bcf8e621-1437-2442-6529-4c0c843e325b@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vkaplans@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 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.