Re: [Xen-devel] [PATCH] tools: misc: xen-tmem-list-parse: fix output ugliness

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
> Sent: Tuesday, November 22, 2011 10:34 AM
> To: Dan Magenheimer
> Cc: Ian Jackson; Stefano Stabellini; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH] tools: misc: xen-tmem-list-parse: fix output 
> ugliness
> 
> On Wed, 2011-11-09 at 21:40 +0000, Dan Magenheimer wrote:
> > (This should apply cleanly to 4.0, 4.1, and unstable.  It would
> > be nice to apply to the next dot release of 4.0 and 4.1, but
> > please definitely apply at least to unstable.)
> >
> > Fix ugly parse output for xen-tmem-list-parse
> >
> > This program parses the output of xm/xl tmem-list into
> > human-readable format.
> 
> Why does xm/xl not just have a human readable output option (or more
> likely, default)?

The raw data originates in the hypervisor in an ASCII format
that was designed to be forward/backward compatible because it
was unclear how much it would need to change over time.
The end consumer is a higher-level management tool; xm/xl
simply pass the data through.  xen-tmem-list-parse acts
as "documentation" for the format and is useful for those
experimenting with tmem.  It didn't seem to make
sense to create an additional dependency for parsing
the format in xm/xl.

Dan

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