Greg KH wrote:
On Thu, Jan 12, 2006 at 09:57:50AM -0600, Anthony Liguori wrote:
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?
Right now it's a string that identifies the type of partition is it (for
instance, "control_d" for the control domain).
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?
Yup.
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.)
Great, thanks!
Regards,
Anthony Liguori
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
