All of lore.kernel.org
 help / color / mirror / Atom feed
From: "KONRAD Frédéric" <fred.konrad@greensocs.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: aliguori@us.ibm.com, e.voevodin@samsung.com,
	mark.burton@greensocs.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, cornelia.huck@de.ibm.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC PATCH v7 7/8] virtio-pci-blk : Switch to new API.
Date: Thu, 13 Dec 2012 09:57:00 +0100	[thread overview]
Message-ID: <50C9985C.8020607@greensocs.com> (raw)
In-Reply-To: <CAFEAcA8HLD-x8=7ZNcg7QsYMBTH7g0QkUsxREkYqy0by+4JF3g@mail.gmail.com>

On 11/12/2012 18:50, Peter Maydell wrote:
> On 10 December 2012 16:45,  <fred.konrad@greensocs.com> wrote:
>> From: KONRAD Frederic <fred.konrad@greensocs.com>
>>
>> Here the virtio-blk-pci is modified for the new API. The device virtio-pci-blk
>> extends virtio-pci. It creates and connects a virtio-blk during the init.
> Did you check whether this maintains backwards compatibility
> for vmstate migration information and device properties?
> (haven't investigated myself yet, just asking whether you have)
>
> -- PMM
What do you mean exactly by backwards compatibility for vmstate migration ?

The device properties didn't change.
The virtio-blk-pci creates a virtio-blk device, puts the virtio block 
properties and  inits the virtio-blk.

  reply	other threads:[~2012-12-13  8:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10 16:45 [Qemu-devel] [RFC PATCH v7 0/8] Virtio refactoring fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 1/8] qdev : add a maximum device allowed field for the bus fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 2/8] virtio-bus : Introduce virtio-bus fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 3/8] virtio-pci-bus : Introduce virtio-pci-bus fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 4/8] virtio-pci : Refactor virtio-pci device fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 5/8] virtio-device : Refactor virtio-device fred.konrad
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 6/8] virtio-blk : Add the virtio-blk device fred.konrad
2012-12-11 17:33   ` Peter Maydell
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 7/8] virtio-pci-blk : Switch to new API fred.konrad
2012-12-11 17:50   ` Peter Maydell
2012-12-13  8:57     ` KONRAD Frédéric [this message]
2012-12-12 14:25   ` Peter Maydell
2012-12-12 17:53     ` Andreas Färber
2012-12-12 17:56       ` Paolo Bonzini
2012-12-12 17:58       ` Peter Maydell
2012-12-12 18:03         ` Paolo Bonzini
2012-12-12 21:22           ` Michael S. Tsirkin
2012-12-13  9:37             ` Paolo Bonzini
2012-12-13 14:51           ` Anthony Liguori
2012-12-16 16:01             ` Michael S. Tsirkin
2012-12-13  9:24         ` KONRAD Frédéric
2012-12-16 16:41       ` Andreas Färber
2012-12-13  8:24     ` KONRAD Frédéric
2012-12-13 10:56       ` KONRAD Frédéric
2012-12-10 16:45 ` [Qemu-devel] [RFC PATCH v7 8/8] virtio-blk : QOM modifications fred.konrad
2012-12-11 17:32   ` Peter Maydell
2012-12-11 17:52 ` [Qemu-devel] [RFC PATCH v7 0/8] Virtio refactoring Peter Maydell

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=50C9985C.8020607@greensocs.com \
    --to=fred.konrad@greensocs.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=e.voevodin@samsung.com \
    --cc=mark.burton@greensocs.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.