Re: [Xen-devel] Re: [RFC] [PATCH] sysfs support for Xen attributes

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

Guys,

I think the waters are getting a bit muddied here regarding Xen (the 
hypervisor, a separate project which boots natively on the hardware, not a 
module or patch to Linux) vs. the Xen Patch to Linux (allowing i386 Linux to 
run on top of that hypervisor's APIs).

> >>The module version? Xen is not a module nor a driver, so that interface
> >>doesn't quite serve the purpose.
> >
> > Then it doesn't need a separate version, as it is the same as the main
> > kernel version, right?  Just because your code is out-of-the-tree right

> > 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.

To put it another way, when Mike referred to "Xen", he meant the hypervisor 
itself, not part of the patch to Linux.  The version attribute under /sys/xen 
is therefore describing the version of the "virtual hardware" that's provided 
by the Xen<->guest OS interface, not for describing / configuring the 
Xen-aware portion of Linux itself.

(side note: Xen's quite like a CPU arch / extended hardware platform in some 
ways, although it's kinda orthogonal to the particular hardware platform in 
use.  Mike - had you looked at how CPU entries are registered 
in /sys/devices/system, for instance?  anything there you could leverage?)

Cheers,
Mark


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel