From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Bastian Blank <waldi@debian.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names
Date: Tue, 01 Jun 2010 09:35:11 -0700 [thread overview]
Message-ID: <4C0536BF.7070605@goop.org> (raw)
In-Reply-To: <1275379012.24218.20337.camel@zakaz.uk.xensource.com>
On 06/01/2010 12:56 AM, Ian Campbell wrote:
> Does any of this logic really belong in libxc in the first place?
>
No. It's a relic of a simpler time.
> Can we not just rip it all out and make it the distro/platform's
> responsibility to ensure these devices exist and are correct? Perhaps
> that might involve shipping some default/example udev rules instead.
>
I only kept it because I didn't want to break any existing installs, but
updating the kernel's name is going to do that anyway. Unfortunately
the current libxc code is broken in the worst possible way - it will
unlink an existing correct device and then fail to replace it - so even
if the system has set it up correctly it will still screw things up.
I think we're just going to have to have a flag day and fix kernel,
libxc and udev (assuming it needs it) all at once...
J
next prev parent reply other threads:[~2010-06-01 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 1:08 [PATCH] xc: deal with xen/evtchn and xen/gntdev device names Jeremy Fitzhardinge
2010-05-29 6:53 ` Bastian Blank
2010-06-01 7:56 ` Ian Campbell
2010-06-01 8:17 ` Bastian Blank
2010-06-01 16:35 ` Jeremy Fitzhardinge [this message]
2010-06-02 9:29 ` Ian Campbell
2010-06-02 16:09 ` Jeremy Fitzhardinge
2010-06-03 8:31 ` Ian Campbell
2010-06-03 19:32 ` Jeremy Fitzhardinge
2010-06-04 9:55 ` Ian Campbell
2010-06-04 10:01 ` Keir Fraser
2010-06-04 15:27 ` Dan Magenheimer
2010-06-04 15:31 ` Ian Campbell
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=4C0536BF.7070605@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@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.