From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Sasha Levin <levinsasha928@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Amit Shah <amit.shah@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Krishna Kumar <krkumar2@in.ibm.com>,
Pawel Moll <pawel.moll@arm.com>,
Wang Sheng-Hui <shhuiw@gmail.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCHv2 RFC] virtio-pci: flexible configuration layout
Date: Mon, 5 Dec 2011 11:16:05 -0800 [thread overview]
Message-ID: <20111205111605.73b60faa@jbarnes-desktop> (raw)
In-Reply-To: <20111114181854.GA24953@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Mon, 14 Nov 2011 20:18:55 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> Add a flexible mechanism to specify virtio configuration layout, using
> pci vendor-specific capability. A separate capability is used for each
> of common, device specific and data-path accesses.
>
> Warning: compiled only.
> This patch also needs to be split up, pci_iomap changes
> also need arch updates for non-x86.
> There might also be more spec changes.
>
> Posting here for early feedback, and to allow Sasha to
> proceed with his "kvm tool" work.
>
> Changes from v1:
> Updated to match v3 of the spec, see:
> Subject: [PATCHv3 RFC] virtio-spec: flexible configuration layout
> Message-ID: <20111110122436.GA13144@redhat.com>
> In-Reply-To: <20111109195901.GA28155@redhat.com>
Looks like this conflicts with your other iomap changes... I didn't
check your latest tree; do you just add another patch on top for the
virtio changes now?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-05 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 18:18 [PATCHv2 RFC] virtio-pci: flexible configuration layout Michael S. Tsirkin
2011-11-14 23:43 ` [RFC 0/5] virtio-pci,kvm tools: Support new virtio-pci spec in kvm tools Sasha Levin
2011-11-14 23:43 ` [RFC 1/5] virtio-pci: flexible configuration layout Sasha Levin
2011-11-21 1:01 ` Rusty Russell
2011-11-14 23:43 ` [RFC 2/5] virtio-pci: Fix compilation issue Sasha Levin
2011-11-14 23:43 ` [RFC 3/5] iomap: Don't ignore offset Sasha Levin
2011-11-14 23:43 ` [RFC 4/5] kvm tools: Free up the MSI-X PBA BAR Sasha Levin
2011-11-14 23:43 ` [RFC 5/5] kvm tools: Support new virtio-pci configuration layout Sasha Levin
2011-11-15 12:59 ` [RFC 0/5] virtio-pci,kvm tools: Support new virtio-pci spec in kvm tools Michael S. Tsirkin
2011-12-05 19:16 ` Jesse Barnes [this message]
2011-12-05 20:20 ` [PATCHv2 RFC] virtio-pci: flexible configuration layout 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=20111205111605.73b60faa@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=aik@ozlabs.ru \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=krkumar2@in.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pawel.moll@arm.com \
--cc=rusty@rustcorp.com.au \
--cc=shhuiw@gmail.com \
--cc=torvalds@linux-foundation.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