From: Amit Shah <amit.shah@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Amos Kong" <akong@redhat.com>,
"qemu list" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/2] virtio-serial: create a linked list of all active devices
Date: Mon, 4 Aug 2014 17:15:00 +0530 [thread overview]
Message-ID: <20140804114500.GP18947@grmbl.mre> (raw)
In-Reply-To: <874mxs32vv.fsf@blackfin.pond.sub.org>
On (Mon) 04 Aug 2014 [13:33:56], Markus Armbruster wrote:
> Amit Shah <amit.shah@redhat.com> writes:
>
> > To ensure two virtserialports don't get added to the system with the
> > same 'name' parameter, we need to access all the ports on all the
> > devices added, and compare the names.
> >
> > We currently don't have a list of all VirtIOSerial devices added to the
> > system. This commit adds a simple linked list in which devices are put
> > when they're initialized, and removed when they go away.
<snip>
> > +struct VirtIOSerialDevices {
> > + QLIST_HEAD(, VirtIOSerial) devices;
> > +} vserdevices;
> > +
>
> Any particular reason for stuffing the list into a struct?
Not strictly needed for this patch alone, but I think it's cleaner to
keep it this way, and when something else comes up that needs a
per-device variable, this list will be around. Also, this is also the
way it's done in the kernel, so that uniformity helps as well.
<snip>
> Patch looks simple & safe to me, but I can't help to wonder whether want
> (or already have?) more generic infrastructure offering "for all devices
> of a certain kind" functionality, which is what 2/2 needs. Andreas?
Yea; I didn't find any, but if there's already something it can be put
to good use here.
Thanks,
Amit
next prev parent reply other threads:[~2014-08-04 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 11:31 [Qemu-devel] [PATCH 0/2] virtio-serial: Prevent addition of ports with same name Amit Shah
2014-07-16 11:31 ` [Qemu-devel] [PATCH 1/2] virtio-serial: create a linked list of all active devices Amit Shah
2014-08-04 11:33 ` Markus Armbruster
2014-08-04 11:45 ` Amit Shah [this message]
2014-08-06 7:27 ` Markus Armbruster
2014-08-06 7:39 ` Amit Shah
2014-08-18 17:21 ` Andreas Färber
2014-08-19 15:45 ` Markus Armbruster
2014-08-19 16:15 ` Andreas Färber
2014-07-16 11:31 ` [Qemu-devel] [PATCH 2/2] virtio-serial: search for duplicate port names before adding new ports Amit Shah
2014-08-06 7:27 ` [Qemu-devel] [PATCH 0/2] virtio-serial: Prevent addition of ports with same name Markus Armbruster
2014-08-06 7:39 ` Amit Shah
2014-08-18 17:10 ` Amit Shah
2014-08-18 17:17 ` Andreas Färber
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=20140804114500.GP18947@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=armbru@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).