From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/5] virtio 1.0 cleanups and one fix.
Date: Sun, 8 Feb 2015 10:52:34 +0100 [thread overview]
Message-ID: <20150208095234.GA3185@redhat.com> (raw)
In-Reply-To: <1423199216-2094-1-git-send-email-rusty@rustcorp.com.au>
On Fri, Feb 06, 2015 at 03:36:51PM +1030, Rusty Russell wrote:
> Hi all,
>
> Some minor fixes for my virtio-next tree. Michael, does
> QEMU implement the (compuslory!) VIRTIO_PCI_CAP_PCI_CFG field? I'm
> guessing not, since it wasn't defined in the Linux header :(
Not yet, thanks for the reminder.
BIOS is going to use that one so you can be sure
it'll be there when support is merged finally.
> Rusty Russell (5):
> virtio: define VIRTIO_PCI_CAP_PCI_CFG in header.
> virtio: Don't expose legacy block features when VIRTIO_BLK_NO_LEGACY
> defined.
> virtio: Don't expose legacy net features when VIRTIO_NET_NO_LEGACY
> defined.
> virtio: Don't expose legacy config features when
> VIRTIO_CONFIG_NO_LEGACY defined.
> virtio: don't require a config space on the console device.
>
> drivers/char/virtio_console.c | 12 ++++++++----
> include/uapi/linux/virtio_blk.h | 17 +++++++++++++----
> include/uapi/linux/virtio_config.h | 2 ++
> include/uapi/linux/virtio_net.h | 30 ++++++++++++++++++++++++++++--
> include/uapi/linux/virtio_pci.h | 4 +++-
> 5 files changed, 54 insertions(+), 11 deletions(-)
>
> --
> 2.1.0
prev parent reply other threads:[~2015-02-08 9:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 5:06 [PATCH 0/5] virtio 1.0 cleanups and one fix Rusty Russell
2015-02-06 5:06 ` [PATCH 1/5] virtio: define VIRTIO_PCI_CAP_PCI_CFG in header Rusty Russell
2015-02-08 11:00 ` Michael S. Tsirkin
2015-02-06 5:06 ` [PATCH 2/5] virtio: Don't expose legacy block features when VIRTIO_BLK_NO_LEGACY defined Rusty Russell
2015-02-08 11:01 ` Michael S. Tsirkin
2015-02-06 5:06 ` [PATCH 3/5] virtio: Don't expose legacy net features when VIRTIO_NET_NO_LEGACY defined Rusty Russell
2015-02-08 10:59 ` Michael S. Tsirkin
2015-02-08 23:50 ` Rusty Russell
2015-02-11 0:06 ` Rusty Russell
2015-02-16 5:14 ` Michael S. Tsirkin
2015-02-16 6:09 ` Rusty Russell
2015-02-14 20:43 ` Michael S. Tsirkin
2015-02-16 3:29 ` Rusty Russell
2015-02-06 5:06 ` [PATCH 4/5] virtio: Don't expose legacy config features when VIRTIO_CONFIG_NO_LEGACY defined Rusty Russell
2015-02-08 11:03 ` Michael S. Tsirkin
2015-02-06 5:06 ` [PATCH 5/5] virtio: don't require a config space on the console device Rusty Russell
2015-02-08 11:03 ` Michael S. Tsirkin
2015-02-08 23:56 ` Rusty Russell
2015-02-11 11:16 ` Amit Shah
2015-02-08 9:52 ` 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=20150208095234.GA3185@redhat.com \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.