From: "Michael S. Tsirkin" <mst@redhat.com>
To: Or Gerlitz <ogerlitz@voltaire.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCHv3 0/2] vhost: a kernel-level virtio server
Date: Wed, 19 Aug 2009 16:10:48 +0300 [thread overview]
Message-ID: <20090819131048.GD3080@redhat.com> (raw)
In-Reply-To: <4A8BB4EF.7030403@Voltaire.com>
On Wed, Aug 19, 2009 at 11:16:47AM +0300, Or Gerlitz wrote:
> Michael S. Tsirkin wrote:
> > The patches are against 2.6.31-rc4. I'd like them to go into linux-next
> > and down the road 2.6.32 if possible. Please comment.
>
> Hi Michael,
>
> Just wanted to make sure with you how this can be tested, is 2.6.31-rc4
> plus these two patches enough to form the kernel part? I wasn't sure if
> both the irqfd/iosignalfd are needed and if both are merged to Linus tree...
No, these patches are on top of Avi's kvm.git
> As for the user space part, should I use upstream qemu plus patches 1-4?
qemu-kvm
> Or.
next prev parent reply other threads:[~2009-08-19 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 18:27 [PATCHv3 0/2] vhost: a kernel-level virtio server Michael S. Tsirkin
2009-08-19 8:16 ` Or Gerlitz
2009-08-19 13:10 ` Michael S. Tsirkin [this message]
2009-08-19 13:44 ` Or Gerlitz
2009-08-19 13:45 ` Michael S. Tsirkin
2009-08-20 13:34 ` Or Gerlitz
2009-08-20 13:39 ` Michael S. Tsirkin
2009-08-20 17:03 ` 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=20090819131048.GD3080@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
/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).