From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Stefan Hajnoczi <stefanha@gmail.com>,
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: Sun, 28 Jul 2013 11:10:45 +0300 [thread overview]
Message-ID: <20130728081045.GM12087@redhat.com> (raw)
In-Reply-To: <CAFEAcA94mzS_JJa6F=ecuHWgMvrMSfJAU-sVDCMXUo1p0qYmPg@mail.gmail.com>
On Fri, Jul 26, 2013 at 10:43:44AM +0100, Peter Maydell wrote:
> On 26 July 2013 10:25, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > On Thu, Jul 25, 2013 at 05:53:06PM +0300, Michael S. Tsirkin wrote:
> >> On Thu, Jul 25, 2013 at 03:12:31PM +0100, Peter Maydell wrote:
> >> > On 25 July 2013 03:08, Anthony Liguori <anthony@codemonkey.ws> wrote:
> >> > > We really ought to strongly deprecate -net because it's misleading.
> >> >
> >> > ...we still need to figure out how -netdev is supposed to
> >> > work for embedded (created-by-default) network devices first.
>
> >> I guess it could work just like -net does: assume a default netdev name?
>
> (for clarity, rather than as an argument against this idea)
> This isn't how -net works : "-net nic,options" sets up an
> entry in the nd_table[], and the board will then pick up those
> entries based on some ad-hoc combination of order and whether
> a model= was specified for that nic.
>
> > Sounds like a simple way to solve it, as long as machines use the
> > standard name(s) for build-in NICs.
>
> How would this work for (for example) specifying a macaddr
> for the built-in NIC? At the moment you can do that with
> -net nic,macaddr=<whatever>.
>
> -- PMM
ATM you can use -global for that.
We generally need a way to specify properties for
built-in devices by path.
--
MST
next prev parent reply other threads:[~2013-07-28 8:09 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
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 [this message]
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=20130728081045.GM12087@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@gmail.com \
--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 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).