From: Greg KH <greg@kroah.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: "Mike D. Day" <ncmike@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
xen-devel@lists.xensource.com
Subject: Re: [RFC] [PATCH] sysfs support for Xen attributes
Date: Thu, 12 Jan 2006 09:38:16 -0800 [thread overview]
Message-ID: <20060112173816.GC10513@kroah.com> (raw)
In-Reply-To: <43C65196.8040402@suse.de>
On Thu, Jan 12, 2006 at 01:54:46PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> >>Huh? You can't just throw a "MODULE_VERSION()", and a module_init()
> >>somewhere into the xen code to get this to happen? Then all of your
> >>configurable paramaters show up automagically.
> >
> >No, I can't. Xen does not have modules. Xen loads and runs linux.
>
> You can. Just look at a recent drivers/xen/blkback/blkback.c, the
> module parameters specified there show up in
> /sys/module/blkback/parameters, no matter whenever the code was built
> statically into the kernel or as module (which curently doesn't work for
> blkback anyway ...).
>
> Any read-only attributes can trivially be implemented that way. Simple
> writable stuff (balloon driver?) probably too, I don't know whenever a
> notify callback on parameter changes is possible though.
Yes it is.
> The current /proc files which are not simple attributes such as
> /proc/xen/{privcmd,xenbus} are a bit more tricky, not sure what the best
> approach for these is. privcmd returns a filehandle which is then used
> for ioctls (misc char dev maybe?). xenbus can be opened and (I think)
> read(2) on to listen for any xenbus activity, much like /proc/kmsg.
> Suggestions what to use here instead of procfs? Or just leave it there?
Your own filesystem? You can do that in about 200 lines of code these
days :)
And no, it does not belong in procfs.
thanks,
greg k-h
next prev parent reply other threads:[~2006-01-12 17:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:17 [RFC] [PATCH] sysfs support for Xen attributes Mike D. Day
2006-01-11 17:19 ` Arjan van de Ven
2006-01-11 17:56 ` Stephen Hemminger
2006-01-11 18:45 ` Dave Hansen
2006-01-11 23:07 ` Greg KH
2006-01-12 0:23 ` Mike D. Day
2006-01-12 0:57 ` Greg KH
2006-01-12 1:49 ` Mike D. Day
2006-01-12 2:17 ` [Xen-devel] " Mark Williamson
2006-01-12 7:10 ` Greg KH
2006-01-12 14:44 ` [Xen-devel] " Mike D. Day
2006-01-12 14:53 ` Mark Williamson
2006-01-12 15:42 ` Anthony Liguori
2006-01-12 15:57 ` Anthony Liguori
2006-01-12 17:34 ` Greg KH
2006-01-12 18:44 ` Anthony Liguori
2006-01-12 17:43 ` Greg KH
2006-01-12 9:10 ` Dave Hansen
2006-01-12 14:52 ` [Xen-devel] " Mike D. Day
2006-01-12 15:28 ` Dave Hansen
2006-01-12 15:50 ` Mike D. Day
2006-01-12 12:54 ` Gerd Hoffmann
2006-01-12 13:21 ` Arjan van de Ven
2006-01-12 14:42 ` Gerd Hoffmann
2006-01-12 17:39 ` Greg KH
2006-01-12 18:53 ` Anthony Liguori
2006-01-12 18:55 ` Arjan van de Ven
2006-01-12 18:59 ` Anthony Liguori
2006-01-12 19:11 ` Mike D. Day
2006-01-12 19:31 ` Greg KH
2006-01-12 19:08 ` Greg KH
2006-01-12 19:18 ` Mike D. Day
2006-01-12 19:30 ` Greg KH
2006-01-12 17:38 ` Greg KH [this message]
2006-01-12 1:32 ` Dave Hansen
2006-01-12 10:04 ` [Xen-devel] " Keir Fraser
2006-01-12 15:14 ` Dave Hansen
2006-01-12 15:06 ` Mark Williamson
2006-01-12 15:26 ` Keir Fraser
2006-01-12 15:37 ` Dave Hansen
2006-01-12 15:49 ` Anthony Liguori
2006-01-11 23:31 ` Pavel Machek
2006-01-12 19:01 ` Greg KH
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=20060112173816.GC10513@kroah.com \
--to=greg@kroah.com \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncmike@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox