[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 2/4] Implement code to read coverage informations
On Wed, 2013-02-06 at 07:51 +0000, Jan Beulich wrote: > >>> On 05.02.13 at 16:58, Frediano Ziglio <frediano.ziglio@xxxxxxxxxx> wrote: > > +/** > > + * File information > > + * Prefixed with XENCOV_TAG_FILE and a string with filename > > + */ > > +struct xencov_file > > +{ > > + uint32_t version; > > + uint32_t stamp; > > +} __attribute__((packed)); > > + > > +/** > > + * Counters information > > + * Prefixed with XENCOV_TAG_COUNTER(n) where n is 0..(XENCOV_COUNTERS-1) > > + */ > > +struct xencov_counter > > +{ > > + uint32_t num; > > + uint64_t values[0]; > > +} __attribute__((packed)); > > + > > +/** > > + * Information for each function > > + * Prefixed with XENCOV_TAG_FUNC > > + * Number of counter is equal to the number of counter got before > > + */ > > +struct xencov_function > > +{ > > + uint32_t ident; > > + uint32_t checksum; > > + uint32_t n_ctrs[0]; > > +} __attribute__((packed)); > > + > > +struct xencov_functions > > +{ > > + uint32_t num; > > + uint32_t xencov_function[0]; > > +} __attribute__((packed)); > > Once again: No use of compiler extensions in public headers. > > Jan > Sorry, I forgot the old mail. Currently this header describe the output blob exported by Xen. For the array I can just use 1 instead of 0. I'm changing a bit the format to avoid packing and alignment problems. Frediano _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |