From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: rusty@rustcorp.com.au, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] virtio: Add PCI memory BAR in addition to PIO BAR
Date: Thu, 03 Nov 2011 15:45:36 +0200 [thread overview]
Message-ID: <4EB29B00.10907@redhat.com> (raw)
In-Reply-To: <4EB2993C.9000902@codemonkey.ws>
On 11/03/2011 03:38 PM, Anthony Liguori wrote:
>>
>>> We could use a better agreement on the processor for making virtio
>>> changes. Should it go (1) virtio spec (2) kernel (3) qemu, or should
>>> it go (2), (1), (3)?
>>
>> 1. Informal discussion
>
>
> Where? Is this lkml? There were a number of virtio changes recently
> that never involved qemu-devel.
Theoretically, virtualization@lists.linux-foundation.org, if it still
exists. Maybe we need a virtio list. qemu-devel@, kvm@, lkml could be
copied.
The point is that we can't drive virtio from either qemu or the kernel
any more. The spec represents the "virtual hardware manufacturer",
which qemu and linux/vhost (and others) emulate, and which linux (and
others) write drivers for.
>
>> 2. Proposed spec patch, kernel change, qemu change
>> 3. Buy-ins from spec maintainer, kernel driver maintainer, qemu device
>> maintainer (only regarding the ABI, not the code)
>
> I don't think this is how it's working today. I would be happy with a
> flow like this.
If Michael and Rusty agree, we can adopt it immediately.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-03 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 5:26 [Qemu-devel] [PATCH] virtio: Add PCI memory BAR in addition to PIO BAR David Gibson
2011-11-01 22:20 ` Anthony Liguori
2011-11-02 0:16 ` David Gibson
2011-11-02 0:32 ` Anthony Liguori
2011-11-02 3:22 ` Rusty Russell
2011-11-02 12:39 ` Anthony Liguori
2011-11-02 21:51 ` Michael S. Tsirkin
2011-11-03 10:36 ` Avi Kivity
2011-11-03 13:07 ` Anthony Liguori
2011-11-03 13:13 ` Avi Kivity
2011-11-03 13:38 ` Anthony Liguori
2011-11-03 13:45 ` Avi Kivity [this message]
2011-11-03 13:49 ` Anthony Liguori
2011-11-03 14:31 ` Michael S. Tsirkin
2011-11-03 14:37 ` Anthony Liguori
2011-11-03 14:53 ` Avi Kivity
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=4EB29B00.10907@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=david@gibson.dropbear.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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 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).