Re: [Xen-devel] [PATCH] nestedhvm: xentrace support

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Thu, Apr 14, 2011 at 3:36 PM, Christoph Egger
<Christoph.Egger@xxxxxxx> wrote:
>> Finally, George may have a
>> reason for not including RIP in VMENTRY records (e.g., not that useful
>> compared with the extra space taken up in trace records). So you'd need to
>> submit a new patch and get an Ack from George (who is currently on
>> holiday).

Yeah, the general principle is just to not log duplicate information,
or information which can be inferred.  VMENTRY logs happen a *lot*,
and so a small change has a non-negligible impact on trace size.  To
this point, I haven't needed the RIP on VMENTRY, since having it on
VMEXIT is generally sufficient.

> Ok. If he has one I would like to know it.
> For nested virtualization it is at least good debugging information to see
> if the l2 guest loops somewhere or not.

Can't you get this information from looking at the RIP on the
corresponding VMEXIT?

 -George

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