All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Liu Yu-B13201 <B13201@freescale.com>
Cc: Yoder Stuart-B08248 <B08248@freescale.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Vhost support
Date: Mon, 21 Feb 2011 13:46:02 +0200	[thread overview]
Message-ID: <20110221114602.GA5557@redhat.com> (raw)
In-Reply-To: <FBDE6FBB4662C043AC9EECB95F62CDDE15E80D@039-SN1MPN1-005.039d.mgd.msft.net>

On Mon, Feb 21, 2011 at 11:41:39AM +0000, Liu Yu-B13201 wrote:
>  
> 
> > -----Original Message-----
> > From: Michael S. Tsirkin [mailto:mst@redhat.com] 
> > Sent: Monday, February 21, 2011 7:22 PM
> > To: Liu Yu-B13201
> > Cc: qemu-devel@nongnu.org; Yoder Stuart-B08248
> > Subject: Re: Vhost support
> > 
> > On Mon, Feb 21, 2011 at 11:13:33AM +0000, Liu Yu-B13201 wrote:
> > > 
> > > Hello everyone,
> > > 
> > > Does anyone know the status of vhost in upstream qemu?
> > > We would like to try vhost with kvm on powerpc e500v2 platform,
> > > but obviously, powerpc kvm only works with upstream qemu.
> > > 
> > > KVM wike page says it needs to enable CONFIG_PCI_MSI for 
> > guest kernel.
> > > Is MSI a necessary?
> > > 
> > > Thanks,
> > > Yu
> > 
> > At the moment, yes.
> > The issue is not with vhost, it's that irqfd in kvm
> > only works with MSI at the moment.
> > 
> 
> Hi Michael,
> 
> Thanks for your answer.
> But I don't find MSI or irqfd support in upstream qemu.
> Does it mean upstream qemu not support virtio/vhost for now?
> 
> 
> Thanks,
> Yu

Ahm you mean not qemu-kvm?  It does, just slowly by going through
userspace.  You can force vhost bouncing without msi as well, by
setting vhostforce.

-- 
MST

  reply	other threads:[~2011-02-21 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 11:13 [Qemu-devel] Vhost support Liu Yu-B13201
2011-02-21 11:22 ` [Qemu-devel] " Michael S. Tsirkin
2011-02-21 11:41   ` [Qemu-devel] " Liu Yu-B13201
2011-02-21 11:46     ` Michael S. Tsirkin [this message]
2011-02-21 11:51       ` Liu Yu-B13201

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=20110221114602.GA5557@redhat.com \
    --to=mst@redhat.com \
    --cc=B08248@freescale.com \
    --cc=B13201@freescale.com \
    --cc=qemu-devel@nongnu.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 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.