 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] [PATCH] nestedhvm: xentrace support
| To: | Christoph Egger <Christoph.Egger@xxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] [PATCH] nestedhvm: xentrace support |
| From: | George Dunlap <George.Dunlap@xxxxxxxxxxxxx> |
| Date: | Mon, 18 Apr 2011 11:22:15 +0100 |
| Cc: | "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx> |
| Delivery-date: | Mon, 18 Apr 2011 03:23:09 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6bIiOtebkjjxMz7q8CCzFsCp4sVMrkfgwrsb6BXpWeU=; b=QNpCrT1G4X+sb8jEH5J1Qc9ts9AoL3ZvJ6hTUFC+sekfKJpxUC8FyE4sE5qtkth+4M 03Q7q5f/PUzi+NzQfZ7LAuR36908HJW22QBSVfB82onkFsI2cCExXsoIMebJcG0yGVId VgGpvasf3mxzVEgBdonMudJ5ubZCe4yzaTXEA= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=gwbgRZc9MsTfYXQ1QQJj9nlWNEEOKvmhe2Bvcln+SkkQGA3aAQSkluvpeuQ6AC6/rF d8F5EjOuICvySeXpBWWZt0XTchAZOWJLGthOmBX9ZujM+APBfKGnsav37PsVS1gVCjZg 9SfOqTIZ/IdkHju/mviSxsCOb9+wC1/WdXC2g= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <4DA70674.2090203@xxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <C9CCBC97.2CA58%keir@xxxxxxx> <4DA70674.2090203@xxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] Can't map the page referenced by HVM-DomU CR3 in Dom0, Tim Deegan |
|---|---|
| Next by Date: | [Xen-devel] Re: [PATCH V2 4/4] amd iommu: interfaces for p2m sharing, Tim Deegan |
| Previous by Thread: | Re: [Xen-devel] [PATCH] nestedhvm: xentrace support, Keir Fraser |
| Next by Thread: | [Xen-devel] [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record, Tim M |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
