From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/6] virtio_balloon: virtio 1 support
Date: Tue, 31 Mar 2015 11:47:41 +0200 [thread overview]
Message-ID: <20150331104725-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <20150331104618.3da249e3.cornelia.huck@de.ibm.com>
On Tue, Mar 31, 2015 at 10:46:18AM +0200, Cornelia Huck wrote:
> On Mon, 30 Mar 2015 19:37:08 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > Virtio 1.0 doesn't include a modern balloon device.
> > At some point we'll likely define an incompatible interface with a different
> > ID. But for now, it's not a big change to support a transitional balloon
> > device: this has the advantage of supporting existing drivers, transparently.
>
> This is needed to support a ballooner on transports that don't support
> mixing legacy and 1.0, right?
That too. But it's also useful if you don't know whether your guest
supports virtio 1 or not - which is the point of using
a transitional device.
> >
> > The only issue is with the stats buffer, which has misaligned fields.
> > Seems easy to fix by prepending a 6 byte reserved field.
>
> I assume you also define the stats fields to be le for 1.0?
They were always le for the balloon.
> >
> > I'll post spec patch and qemu patches shortly.
>
> I'll defer review until then.
>
> >
> > Michael S. Tsirkin (6):
> > virtio_balloon: transitional interface
> > virtio: balloon might not be a legacy device
> > virtio_ccw: support non-legacy balloon devices
> > virtio_mmio: support non-legacy balloon devices
> > virtio_pci: support non-legacy balloon devices
> > virtio: drop virtio_device_is_legacy_only
> >
> > include/linux/virtio.h | 2 --
> > include/uapi/linux/virtio_balloon.h | 6 ++++++
> > drivers/s390/kvm/virtio_ccw.c | 10 +++-------
> > drivers/virtio/virtio.c | 6 ------
> > drivers/virtio/virtio_balloon.c | 8 ++++++--
> > drivers/virtio/virtio_mmio.c | 8 --------
> > drivers/virtio/virtio_pci_modern.c | 3 ---
> > 7 files changed, 15 insertions(+), 28 deletions(-)
> >
prev parent reply other threads:[~2015-03-31 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 17:37 [PATCH 0/6] virtio_balloon: virtio 1 support Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 1/6] virtio_balloon: transitional interface Michael S. Tsirkin
2015-03-30 17:55 ` Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 2/6] virtio: balloon might not be a legacy device Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 3/6] virtio_ccw: support non-legacy balloon devices Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 4/6] virtio_mmio: " Michael S. Tsirkin
2015-03-31 12:31 ` Pawel Moll
2015-03-31 19:51 ` Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 5/6] virtio_pci: " Michael S. Tsirkin
2015-03-30 17:37 ` [PATCH 6/6] virtio: drop virtio_device_is_legacy_only Michael S. Tsirkin
2015-03-31 8:46 ` [PATCH 0/6] virtio_balloon: virtio 1 support Cornelia Huck
2015-03-31 9:47 ` Michael S. Tsirkin [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=20150331104725-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtio-dev@lists.oasis-open.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox