Hi,

Xen tracing some times ago used to put values of type 'long' into the 
trace buffer. This has changed to uint32_t. Some trace points log 
virtual addresses, which get cropped to 32bit in this case. There were 
some inline functions to handle at least PF_XEN and VMEXIT, which caused 
a lot of code duplication. The attached patch fixes several issues:
1. fix and extend tools/xentrace/formats
2. Fix xentrace_format to handle up to 7 parameters
3. create convenience macros to properly log long values
4. remove the inline functions in hvm/trace.h and replace them by macros
5. Change the CPUID trace to work correctly
6. group HVM trace points enable mechanism

I used a similar approach as in PV tracing with bit 8 indicating 64bit 
pointers.

Discussion welcome!

Signed-off-by: Andre Przywara <andre.przywara@amd.com>

BTW: Why is xentrace_format so awfully slow? I have rewritten the tool 
in C and reached a speedup of more than 20 times. If someone bugs me I 
will share the code...

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy