From: Mark McLoughlin <markmc@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 0/3] qdev-ify network cards
Date: Wed, 30 Sep 2009 08:20:30 +0100 [thread overview]
Message-ID: <1254295230.3105.12.camel@blaa> (raw)
In-Reply-To: <1253907783-1231-1-git-send-email-kraxel@redhat.com>
On Fri, 2009-09-25 at 21:43 +0200, Gerd Hoffmann wrote:
> Hi,
>
> Short RfC patch series to get the discussion rolling. We really need to
> get the nic drivers qdev-ified properly, so qemu stops segfaulting on
> '-device $any_nic_here'.
>
> To keep things small simple I've started with the ne2k_isa. All the PCI
> nics share the initialization path and thus I can't simply pick a single
> one as example and convert it.
>
> The network card can now be created using ...
>
> -device ne2k_isa,mac=00:11:22:33:44:55,vlan=0,irq=3,id=foo
>
> 'info qtree' shows ...
>
> [ ... ]
> bus: isa.0
> type ISA
> dev: ne2k_isa, id "foo"
> dev-prop: iobase = 0x300
> dev-prop: irq = 3
> dev-prop: vlan = 1
> dev-prop: mac = 00:11:22:33:44:55
> [ ... ]
>
> 'info network' shows:
>
> [ ... ]
> VLAN 1 devices:
> foo: model=ne2k_isa,macaddr=00:11:22:33:44:55
>
> The nic initialization code calls qemu_new_vlan_client() with the
> vlan specified using the vlan property.
One thing I'd like to see is that if vlan= isn't specified, the nic
shouldn't be connected to any vlan.
I want to add the option to connect a nic directly to a backend without
any vlan involved. That implies you should be able to create a
disconnected nic and later connect it to a backend. Assuming vlan=0
where none is specified makes that difficult.
Patches look fine otherwise.
Cheers,
Mark.
next prev parent reply other threads:[~2009-09-30 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 19:43 [Qemu-devel] [RfC PATCH 0/3] qdev-ify network cards Gerd Hoffmann
2009-09-25 19:43 ` [Qemu-devel] [RfC PATCH 1/3] net: macaddr tweaks Gerd Hoffmann
2009-09-28 22:42 ` Markus Armbruster
2009-09-29 9:24 ` Gerd Hoffmann
2009-09-30 11:57 ` [Qemu-devel] " Paolo Bonzini
2009-09-30 17:19 ` Blue Swirl
2009-09-25 19:43 ` [Qemu-devel] [RfC PATCH 2/3] qdev: mac addr property fixups Gerd Hoffmann
2009-09-25 19:43 ` [Qemu-devel] [RfC PATCH 3/3] ne2k_isa: qdev-ify Gerd Hoffmann
2009-09-28 22:50 ` [Qemu-devel] [RfC PATCH 0/3] qdev-ify network cards Markus Armbruster
2009-09-30 7:20 ` Mark McLoughlin [this message]
2009-09-30 9:07 ` Gerd Hoffmann
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=1254295230.3105.12.camel@blaa \
--to=markmc@redhat.com \
--cc=kraxel@redhat.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 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).