From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>,
xen-devel@lists.xensource.com,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Name of event-channel and other devices vs. udev
Date: Thu, 27 May 2010 15:05:10 -0700 [thread overview]
Message-ID: <4BFEEC96.3010207@goop.org> (raw)
In-Reply-To: <20100527143104.GB6040@wavehammer.waldi.eu.org>
On 05/27/2010 07:31 AM, Bastian Blank wrote:
> On Thu, May 27, 2010 at 09:35:12AM +0200, Bastian Blank wrote:
>
>> On Wed, May 26, 2010 at 12:51:44PM +0200, Bastian Blank wrote:
>>
>>> - 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.
>>
> Xen themself is responsible for this behaviour.
>
You presumably don't mean the hypervisor. Do you mean the toolstack is
doing something bad when the misc device has a '/' in it? I noticed
when I applied your change it does things like look in
/sys/class/xen/evtchn (or something).
What other changes are needed to keep things working after this change?
J
next prev parent reply other threads:[~2010-05-27 22:05 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
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 ` Jeremy Fitzhardinge [this message]
2010-05-27 22:26 ` Name of event-channel and other devices vs. udev 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=4BFEEC96.3010207@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=waldi@debian.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.