All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] vhost acceleration broken?
Date: Thu, 25 Jul 2013 17:52:15 +0300	[thread overview]
Message-ID: <20130725145215.GA3758@redhat.com> (raw)
In-Reply-To: <87ppu66a73.fsf@codemonkey.ws>

On Thu, Jul 25, 2013 at 08:28:00AM -0500, Anthony Liguori wrote:
> Rusty Russell <rusty@rustcorp.com.au> writes:
> 
> > Anthony Liguori <anthony@codemonkey.ws> writes:
> >> On Wed, Jul 24, 2013 at 8:55 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
> >>> Hi all,
> >>>
> >>>         Using latest kernel and master qemu, the following doesn't use
> >>> vhost acceleration:
> >>>
> >>> sudo qemu-system-x86_64 -machine pc,accel=kvm $ARGS -m 1024 -net tap,script=/home/rusty/bin/kvm-ifup,downscript=no,vhost=on -net nic,model=virtio -drive file=$QEMUIMAGE,index=0,media=disk,if=virtio -kernel arch/x86/boot/bzImage -append "root=/dev/vda1 $KARGS $*"
> >>
> >> sudo qemu-system-x86_64 -enable-kvm $ARGS -m 1G -netdev
> >> tap,script=/home/rusty/bin/kvm-ifup,vhost=on,id=net0 -device
> >> virtio-net-pci,netdev=net0 -drive file=$QEMUIMAGE,if=virtio -kernel
> >> arch/x86/boot/bzImage -append "root=/dev/vda1 $KARGS $*"
> >>
> >> We really ought to strongly deprecate -net because it's misleading.  I
> >> suspect we can reasonably add a warning for model=virtio saying
> >> "please don't use this" and eventually remove it entirely.
> >
> > Thankyou, that works.
> >
> > I'm sure you've thought more deeply about the qemu cmdline than I have,
> > so I won't comment.
> 
> Any comment you would make is certainly fair.
> 
> We have a pretty awful legacy command line set that comes from years of
> half-baked concepts and the years when too many people just committed
> random shit to the tree.
> 
> I think we probably need to start planning for a clean break.  Maybe
> that's a good target for a 2.0 version...
> 
> Regards,
> 
> Anthony Liguori
> 
> >
> > Cheers,
> > Rusty.

Assuming -netdev supports all required configurations, we should
remove -net from the -help output.

  reply	other threads:[~2013-07-25 14:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  1:55 [Qemu-devel] vhost acceleration broken? Rusty Russell
2013-07-25  2:08 ` Anthony Liguori
2013-07-25  3:07   ` Rusty Russell
2013-07-25 13:28     ` Anthony Liguori
2013-07-25 14:52       ` Michael S. Tsirkin [this message]
2013-07-25 14:56         ` Andreas Färber
2013-07-25 15:24           ` Michael S. Tsirkin
2013-07-25 16:16             ` Anthony Liguori
2013-07-25 16:20               ` Peter Maydell
2013-07-25 16:32                 ` Michael S. Tsirkin
2013-07-28 23:55               ` Rusty Russell
2013-07-29  2:10                 ` Anthony Liguori
2013-07-29  7:33                   ` Michael S. Tsirkin
2013-07-29  7:09                 ` Michael S. Tsirkin
2013-07-25 14:12   ` Peter Maydell
2013-07-25 14:53     ` Michael S. Tsirkin
2013-07-26  9:25       ` Stefan Hajnoczi
2013-07-26  9:43         ` Peter Maydell
2013-07-28  8:10           ` Michael S. Tsirkin
2013-07-25  5: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=20130725145215.GA3758@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=stefanha@redhat.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 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.