All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: e.voevodin@samsung.com, mark.burton@greensocs.com,
	qemu-devel@nongnu.org, stefanha@redhat.com,
	cornelia.huck@de.ibm.com, afaerber@suse.de,
	"KONRAD Frédéric" <fred.konrad@greensocs.com>
Subject: Re: [Qemu-devel] [RFC PATCH v6 0/6] Virtio refactoring.
Date: Mon, 07 Jan 2013 15:32:14 -0600	[thread overview]
Message-ID: <8762381xy9.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130107204938.GB10575@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:

> On Mon, Jan 07, 2013 at 08:02:32PM +0000, Peter Maydell wrote:
>> On 7 January 2013 19:58, Michael S. Tsirkin <mst@redhat.com> wrote:
>> > On Tue, Dec 18, 2012 at 12:30:20PM +0100, KONRAD Frédéric wrote:
>> >> The modifications will be transparent to the user, as we will keep
>> >> virtio-x-pci devices.
>> >
>> > Then what's the point of all this?
>> >
>> > -device virtio-pci,id=transport1 -device virtio-net,bus=transport1
>> >
>> > or
>> >
>> > -device virtio-mmio,id=transport1 -device virtio-net,bus=transport1
>> >
>> > Is simply an insane way to create a network device.
>> 
>> 1. You wouldn't create the virtio-mmio transport on the command line,
>> the machine model does it (it has to because it's a sysbus device
>> and it needs the address/irq lines wiring up properly), so it's just
>>  "-device virtio-net" (and let qemu find the bus automatically)
>
> Bus auto-detection sounds good and would be nice for pci too.
> We had things like model=virtio originally which is pretty close.
> But the issue is, how then do you pass bus specific arguments like pci
> slot? This is what caused us to go the virtio-net-pci route
> to begin with.

PCI is not the same as MMIO here.

virtio-mmio devices are not pluggable.  It makes a lot more sense to
have a virtio-net-pci device.  But it doesn't make much sense to have a
virtio-net-mmio device.

>
>> 2. We shouldn't be making command line simplicity drive how we
>> model devices inside QEMU.
>
> Confused.  I was told that enabling
>  -device virtio-pci,id=transport1 -device virtio-net,bus=transport1
> is the reason we have this patchset.

You were misinformed.

>> If we wanted to do that we should have
>> stuck with the old -net command line arguments which are rather
>> more userfriendly IMHO.
>
> The main thing that confused people with -net was the vlans
> and the need to specify -net twice.
> A good UI would have been e.g. -nic model=virtio,net=user.

That was the original UI.  It was even called -nics.  See
7c9d8e if you're curious.  I was never a fan of the -net syntax.

> But one bad UI does not justify another one.
>
>> If commandline confusion is getting to
>> be a problem with all the -device foo stuff then we should probably
>> fix that at the UI level.
>> 
>> -- PMM
>
> I'd like to see a proposal about how we are going to do this.

(1) Stop conflating internal modeling with UI

(2) Add UI interfaces as appropriate 

It's really that simple.

Regards,

Anthony Liguori

>
> -- 
> MST

  reply	other threads:[~2013-01-07 21:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 13:32 [Qemu-devel] [RFC PATCH v6 0/6] Virtio refactoring fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 1/6] qdev : add a maximum device allowed field for the bus fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 2/6] virtio-bus : Introduce virtio-bus fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 3/6] virtio-pci-bus : Introduce virtio-pci-bus fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 4/6] virtio-pci : Refactor virtio-pci device fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 5/6] virtio-device : Refactor virtio-device fred.konrad
2012-12-07 13:32 ` [Qemu-devel] [RFC PATCH v6 6/6] virtio-blk : Add the virtio-blk device fred.konrad
2012-12-07 14:53   ` Peter Maydell
2012-12-17 15:45 ` [Qemu-devel] [RFC PATCH v6 0/6] Virtio refactoring Michael S. Tsirkin
2012-12-17 17:13   ` KONRAD Frédéric
2012-12-17 20:46     ` Michael S. Tsirkin
2012-12-18 10:33   ` Peter Maydell
2012-12-18 11:01     ` Michael S. Tsirkin
2012-12-18 11:26       ` Peter Maydell
2012-12-18 11:50         ` Paolo Bonzini
2012-12-18 12:06           ` Peter Maydell
2012-12-18 13:10             ` Michael S. Tsirkin
2012-12-18 14:00               ` Peter Maydell
2012-12-18 14:36                 ` Paolo Bonzini
2012-12-18 14:56                   ` Peter Maydell
2012-12-18 14:59                     ` Paolo Bonzini
2012-12-18 15:42                       ` Michael S. Tsirkin
2012-12-18 15:14                     ` Michael S. Tsirkin
2012-12-18 14:51                 ` Michael S. Tsirkin
2012-12-18 11:30       ` KONRAD Frédéric
2012-12-18 13:21         ` Michael S. Tsirkin
2013-01-07 20:12           ` Anthony Liguori
2013-01-07 20:59             ` Michael S. Tsirkin
2013-01-07 21:24               ` Anthony Liguori
2013-01-07 21:37                 ` Michael S. Tsirkin
2013-01-07 21:51                   ` Anthony Liguori
2013-01-07 22:15                     ` Michael S. Tsirkin
2013-01-07 22:50                       ` Anthony Liguori
2013-01-08  6:46                         ` Michael S. Tsirkin
2013-01-07 22:16                 ` Michael S. Tsirkin
2013-01-07 19:58         ` Michael S. Tsirkin
2013-01-07 20:02           ` Peter Maydell
2013-01-07 20:49             ` Michael S. Tsirkin
2013-01-07 21:32               ` Anthony Liguori [this message]
2013-01-07 20:14           ` Anthony Liguori
2013-01-08  9:56           ` KONRAD Frédéric
2013-01-08 14:02             ` Michael S. Tsirkin
2013-01-08 14:27               ` KONRAD Frédéric

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=8762381xy9.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=e.voevodin@samsung.com \
    --cc=fred.konrad@greensocs.com \
    --cc=mark.burton@greensocs.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --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.