virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, penberg@kernel.org,
	mingo@elte.hu
Subject: Re: [RFC 0/5] virtio-pci,kvm tools: Support new virtio-pci spec in kvm tools
Date: Tue, 15 Nov 2011 14:59:12 +0200	[thread overview]
Message-ID: <20111115125911.GD31208@redhat.com> (raw)
In-Reply-To: <1321314197-5265-1-git-send-email-levinsasha928@gmail.com>

On Tue, Nov 15, 2011 at 01:43:12AM +0200, Sasha Levin wrote:
> This patch series contains two fixes for the RFC patch send by Michael. These
> patches are pretty basic and should probably be merged into the next version
> of that patch.

Yes, will do, thanks!

> Other two patches add support to the new virtio-pci spec in KVM tools, allowing
> for easy testing of any future virtio-pci kernel side patches. The usermode code
> isn't complete, but it's working properly and should be enough for functionality
> testing.
> 
> Michael S. Tsirkin (1):
>   virtio-pci: flexible configuration layout
> 
> Sasha Levin (4):
>   virtio-pci: Fix compilation issue
>   iomap: Don't ignore offset
>   kvm tools: Free up the MSI-X PBA BAR
>   kvm tools: Support new virtio-pci configuration layout
> 
>  drivers/virtio/virtio_pci.c        |  184 ++++++++++++++++++++++--
>  include/asm-generic/io.h           |    4 +
>  include/asm-generic/iomap.h        |   11 ++
>  include/linux/pci_regs.h           |    4 +
>  include/linux/virtio_pci.h         |   41 ++++++
>  lib/iomap.c                        |   41 +++++-
>  tools/kvm/include/kvm/pci.h        |   13 ++-
>  tools/kvm/include/kvm/virtio-pci.h |    5 +-
>  tools/kvm/virtio/pci.c             |  275 ++++++++++++++++++++++++++++++++----
>  9 files changed, 530 insertions(+), 48 deletions(-)
> 
> -- 
> 1.7.8.rc1

  parent reply	other threads:[~2011-11-15 12:59 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   ` Michael S. Tsirkin [this message]
2011-12-05 19:16 ` [PATCHv2 RFC] virtio-pci: flexible " Jesse Barnes
     [not found] ` <20111205111605.73b60faa@jbarnes-desktop>
2011-12-05 20:20   ` 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=20111115125911.GD31208@redhat.com \
    --to=mst@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.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;
as well as URLs for NNTP newsgroup(s).