Anthony Liguori wrote:
quoted text
> If xen-32.0 should be compatible than wouldn't xen-24.0 be compatible
> too?  I think the point was that you should either be checking for
> 'xen-3.x' or something more general that would accept anything >=
> xen-3.0.

The signature is supposed to be an ABI signature, so regardless of the
actual hypervisor version, it should always present "xen-3.0"
(presumably backwards compat if it also supports other versions of the
ABI).  There was a bug in some versions where it puts the actual
hypervisor version in there, requiring this patch.  Technically that
means that looking for "xen-3." is more accurate, but frankly not
important enough to bother raising a patch over.

    J
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/