From: Bastian Blank <waldi@debian.org>
To: xen-devel@lists.xensource.com,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Name of event-channel and other devices vs. udev
Date: Thu, 27 May 2010 09:35:12 +0200 [thread overview]
Message-ID: <20100527073512.GA17135@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <20100526105144.GA28280@wavehammer.waldi.eu.org>
On Wed, May 26, 2010 at 12:51:44PM +0200, Bastian Blank wrote:
> Currently udev overwrites the name of the event-channel device to
> /dev/xen/evtchn. This approach is about to be discontinued and needs to
> be fixed on either side.
> There are several fixes for that:
> - Make the kernel name the device "xen/evtchn".
This approach somewhat reliable failed for me[1]. Also nothing else in
the kernel uses it. So I assume this is not really supported.
> - Remove the rule and convert to another name. Either /dev/evtchn, which
> is a bit to generic or something like xen-evtchn.
So this is the only solution, and the kernel usually uses _ as
delimiter for devices, so "xen_evtchn" is the name to use. And make
xen/evtchn a symlink for backward compatibility.
Bastian
[1]: http://bugs.debian.org/583283
--
Conquest is easy. Control is not.
-- Kirk, "Mirror, Mirror", stardate unknown
next prev parent reply other threads:[~2010-05-27 7:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:51 Name of event-channel and other devices vs. udev Bastian Blank
2010-05-27 0:08 ` Jeremy Fitzhardinge
2010-05-27 7:35 ` Bastian Blank [this message]
2010-05-27 14:31 ` Bastian Blank
2010-05-27 15:02 ` [PATCH] Fix name of Xen event-channel device Bastian Blank
2010-05-27 16:26 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-05-27 16:50 ` Michael Tokarev
2010-05-27 17:13 ` Bastian Blank
2010-05-28 13:24 ` Kay Sievers
2010-05-28 13:41 ` Michael Tokarev
2010-05-28 23:20 ` Jeremy Fitzhardinge
2010-05-27 22:05 ` Name of event-channel and other devices vs. udev Jeremy Fitzhardinge
2010-05-27 22:26 ` Bastian Blank
2010-05-27 22:37 ` Jeremy Fitzhardinge
2010-05-27 22:58 ` Bastian Blank
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=20100527073512.GA17135@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.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.