Re: [Xen-devel] wrong vmexit size in xenalyze

[Keir Fraser <keir@xxxxxxx>]

On 19/11/2010 09:50, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:

> Yeah, doing some archeology... looks like the trace size for the
> HVMTRACE_ND macro is has an off-by-one error since domain_id and vcpu_id
> were removed from HVM trace records in September 2008.
> 
> Tracing is definitely not a stable ABI between releases, but it should
> be reasonably stable after a release.
> 
> Originally I tried having xenalyze detect and deal with different trace
> layouts, but it made the code just too much of a mess.  I could have
> simply tagged xenalyze on a release, but then future improvements to
> xenalyze wouldn't be able to be used on released versions of Xen.

If there are a broader range of incompatibilties between 4.0 and 4.1 then
that makes sense. If the interface is pretty stable now, and it's just one
or two things like this, then maybe it was worth handling automatically.

 -- Keir



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