All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: Greg KH <greg@kroah.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 13:54:46 +0100	[thread overview]
Message-ID: <43C65196.8040402@suse.de> (raw)
In-Reply-To: <43C5B59C.8050908@us.ibm.com>

   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.

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?

cheers,

   Gerd

-- 
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@suse.de>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: Greg KH <greg@kroah.com>,
	xen-devel@lists.xensource.com,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [PATCH] sysfs support for Xen attributes
Date: Thu, 12 Jan 2006 13:54:46 +0100	[thread overview]
Message-ID: <43C65196.8040402@suse.de> (raw)
In-Reply-To: <43C5B59C.8050908@us.ibm.com>

   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.

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?

cheers,

   Gerd

-- 
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.

  parent reply	other threads:[~2006-01-12 12:54 UTC|newest]

Thread overview: 61+ 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 18:45   ` Dave Hansen
2006-01-11 23:07 ` Greg KH
2006-01-12  0:23   ` Mike D. Day
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  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:44             ` Mike D. Day
2006-01-12 14:53             ` [Xen-devel] " Mark Williamson
2006-01-12 15:42               ` Anthony Liguori
2006-01-12 15:57             ` Anthony Liguori
2006-01-12 15:57               ` Anthony Liguori
2006-01-12 17:34               ` [Xen-devel] " 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  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:28               ` Dave Hansen
2006-01-12 15:50               ` [Xen-devel] " Mike D. Day
2006-01-12 15:50                 ` Mike D. Day
2006-01-12 12:54         ` Gerd Hoffmann [this message]
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 18:59                       ` Anthony Liguori
2006-01-12 19:11                       ` Mike D. Day
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:18                       ` Mike D. Day
2006-01-12 19:30                       ` Greg KH
2006-01-12 17:38           ` Greg KH
2006-01-12  1:32     ` Dave Hansen
2006-01-12  1:32       ` Dave Hansen
2006-01-12 10:04       ` [Xen-devel] " Keir Fraser
2006-01-12 10:04         ` Keir Fraser
2006-01-12 15:14         ` [Xen-devel] " Dave Hansen
2006-01-12 15:14           ` Dave Hansen
2006-01-12 15:06           ` [Xen-devel] " Mark Williamson
2006-01-12 15:06             ` Mark Williamson
2006-01-12 15:26           ` [Xen-devel] " Keir Fraser
2006-01-12 15:37             ` Dave Hansen
2006-01-12 15:37               ` Dave Hansen
2006-01-12 15:49               ` [Xen-devel] " Anthony Liguori
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=43C65196.8040402@suse.de \
    --to=kraxel@suse.de \
    --cc=greg@kroah.com \
    --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 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.