From: Amit Shah <amit.shah@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: virtualization@lists.linux-foundation.org,
Linus Walleij <linus.walleij@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC] virtio_console: Add DRIVER and INTERFACE to uevent.
Date: Fri, 25 Jan 2013 14:57:08 +0530 [thread overview]
Message-ID: <20130125092708.GD30483@amit.redhat.com> (raw)
In-Reply-To: <20130124165139.GE15208@kroah.com>
On (Thu) 24 Jan 2013 [08:51:39], Greg KH wrote:
> On Thu, Jan 24, 2013 at 02:30:59PM +0100, Sjur Brændeland wrote:
> > Another approach could perhaps be to change the way port-names are
> > generated by virtio_console...
>
> How would that help here?
>
> The way to solve this is to provide userspace with some "unique"
> identifier of your device. Traditionally that is done with a number of
> different methods:
> - serial numbers and other unique strings in sysfs files
> - device paths (plugged into the 3rd port on the 4th USB device)
> - a "label" in the device (think about filesystems)
virtio-console does have a concept of port 'names'. For example,
the QEMU guest agent knows it just has to open ports available with
the /dev/virtio-ports/org.qemu.guest-agent* names. Sjur, if you add
minimal support for multiport, and use the VIRTIO_CONSOLE_PORT_NAME
feature, this should be already supported by udev.
Amit
prev parent reply other threads:[~2013-01-25 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 12:23 [RFC] virtio_console: Add DRIVER and INTERFACE to uevent sjur.brandeland
2013-01-21 23:25 ` Rusty Russell
2013-01-22 16:16 ` Greg KH
2013-01-24 13:30 ` Sjur Brændeland
2013-01-24 16:51 ` Greg KH
2013-01-25 9:27 ` Amit Shah [this message]
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=20130125092708.GD30483@amit.redhat.com \
--to=amit.shah@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.