 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] mem_access
| To: | super lotion <superlotion51@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] mem_access |
| From: | Aravindh Puthiyaparambil <aravindh@xxxxxxxxxxxx> |
| Date: | Mon, 22 Aug 2011 20:54:48 -0700 |
| Cc: | "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Mon, 22 Aug 2011 20:56:28 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtuata.com; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JYEUxA3y4nnusjoxOpGlwlMw1RmpfImskHwDSbzF+WA=; b=apCd+XjEZV5SKQM99esAynNH8aYxb1VRiLFZf12jjyxNIppaNc6r2Hws+YRuW9IuUv dWWFUeuXd0ib8Jyl5oBXSYN2kjVRui0r2vC0p3btVUvIPzInes6ZtNKL1ldeIoRPhRiD 5u27VeWs4pWAKaGbrSemJBTIhO/0he59xW24s= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <CAGU+auvGkkFzuKKWtuUb_wjgNVzXRwJ1zV_1_cMfhT6SyYEXoQ@xxxxxxxxxxxxxx> |
| 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: | <1313958267.90451.YahooMailNeo@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAGU+auvGkkFzuKKWtuUb_wjgNVzXRwJ1zV_1_cMfhT6SyYEXoQ@xxxxxxxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
> I heard the latest release of Xen includes an API called mem_access. If I'm > interested in analyzing memory accesses HVM guests are making, would this > api help? Also, I can't seem to find any documentation on it or where it is > even located in the xen source tree. Can anyone point me in the right > direction? Take a look at ept_handle_violation() and tools/tests/xen-access in the xen tree. This is a bare bone example of a mem_access event listener. You can work your way back to the source from there. BTW, the API requires you to run on an Intel CPU with EPT support. Aravindh _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] RE: [PATCH] Fix xen hang on intel westmere-EP, Zhang, Yang Z |
|---|---|
| Next by Date: | [Xen-devel] [xen-unstable test] 8722: regressions - FAIL, xen . org |
| Previous by Thread: | [Xen-devel] mem_access, super lotion |
| Next by Thread: | [Xen-devel] [xen-unstable test] 8722: regressions - FAIL, xen . org |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
