All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: "Mike D. Day" <ncmike@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] [RFC] sysfs support for xen linux
Date: Wed, 11 Jan 2006 10:50:56 -0600	[thread overview]
Message-ID: <43C53770.1090403@us.ibm.com> (raw)
In-Reply-To: <200601111628.49811.mark.williamson@cl.cam.ac.uk>

Mark Williamson wrote:

>>Yes, true. I think privcmd might be more appropriate for /proc, but
>>would like to see how it works as a binary file under /sys. ioctl's are
>>not supported by sysfs that I can see, so privcmd would have to be a
>>read/write interface.
>>
>>Regardless of privcmd there are numerous simple attributes related to
>>Xen that are consistent with "zen" of sysfs. :-)
>>    
>>
>
>Agreed.  It's an ideal place for many of the things that are in proc, and many 
>things we'd want to add in the future.
>
>You could possibly abuse sysfs into supporting ioctl but I'm pretty sure the 
>kernel people would find that quite distressing ;-)  I had the impression 
>binary files under sysfs were also a no-no (all meant to be cat-able - 
>addressing one of the other problems of /proc), but I could be mistaken.
>  
>
There was a discussion a while back about this.

http://permalink.gmane.org/gmane.comp.emulators.xen.devel/14273

I think the consensus was to move any ioctl interface to a char device 
and everything else to sysfs.

You'll probably want a proper kobject hierarchy too which means working 
with GKH et al to figure out where out stuff should be 
(/sys/hypervisor/xen??)

Regards,

Anthony Liguori

>Cheers,
>Mark
>
>  
>

  reply	other threads:[~2006-01-11 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 16:28 [PATCH] [RFC] sysfs support for xen linux Mike D. Day
2006-01-11 16:28 ` Mark Williamson
2006-01-11 16:50   ` Anthony Liguori [this message]
2006-01-11 17:03     ` Daniel Stekloff
  -- strict thread matches above, loose matches on Subject: below --
2006-01-11 16:12 Mike D. Day
2006-01-11 16:05 ` Mark Williamson
2006-01-11 16:35   ` Keir Fraser
2006-01-11 16:40     ` Ronald G Minnich
2006-01-10 12:58 Mike D. Day
2006-01-11 10:21 ` Keir Fraser
2006-01-09 23:35 Mike D. Day
2006-01-10  1:09 ` Christopher G. Stach II
2006-01-10 10:13 ` Keir Fraser
2006-01-10 13:23 ` Gawain Lynch
2006-01-12  1:44 ` Chris Wright

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=43C53770.1090403@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --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.