|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [RFC] Cleaning up /proc/xen
Today, in /proc/xen we have:
/proc/xen/balloon - displays information about memory allocations and
allows for ballooning by echoing a byte value into file
/proc/xen/privcmd - allows for userspace invocation of hypercalls and
mapping of other domains memory
/proc/xen/grant - allows grant table operations to be accessed from
userspace
/proc/xen/xenbus - allows xenbus to be accessed from userspace (in domUs)
I propose we do the following:
Change /proc/xen/{privcmd,grant,xenbus} to character devices (that use
random major/minors; we'll always access them by name). We have a few
options for /proc/xen/balloon. We could:
1) Get rid of it completely--not sure it's a good idea but it's been
suggested since it's redundant (in dom0 at least).
2) Move it to /proc/sys/
3) Move it to /sys/xen
I'm partial to the last option (maybe even /sys/hypervisor/xen--that
seems to compliment /sys/firmware).
Thoughts?
Regards,
Anthony Liguori
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [RFC] Cleaning up /proc/xen,
Anthony Liguori <=
|
|
|
|
|