On Thu, Jan 12, 2006 at 09:57:50AM -0600, Anthony Liguori wrote:Right now it's a string that identifies the type of partition is it (for instance, "control_d" for the control domain).
Here's a list of the remaining things we current expose in /proc/xen that have no obvious place:
1) capabilities (is the domain a management domain)
Is this just a single value or a bitfield?
Yup.2) xsd_mfn (a frame number for our bus so that userspace can connect to it)
Single number, right?
Yup.3) xsd_evtchn (a virtual IRQ for xen bus for userspace)
Again, single number?
Great, thanks!I would think these would most obviously go under something like:
/sys/hypervisor/xen/
That would introduce a hypervisor subsystem. There are at least a few hypervisors out there already so this isn't that bad of an idea (although perhaps it may belong somewhere else in the hierarchy). Greg?
I would have no problem with /sys/hypervisor/xen/ as long as you play by
the rest of the rules for sysfs (one value per file, no binary blobs
being intrepreted by the kernel, etc.)
thanks,
greg k-h