This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] accessing hvm-domU memory from dom0

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] accessing hvm-domU memory from dom0
From: david <david_n@xxxxxx>
Date: Tue, 04 Jan 2011 15:19:02 +0100
Delivery-date: Tue, 04 Jan 2011 06:19:46 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D1B8175.9000600@xxxxxx>
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: <4D0F9100.8020003@xxxxxx> <1292925738.4500.1371.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D1B8175.9000600@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7

I have an additional question: Is it possible to access the pseudo physical memory of a hvm-domU in dom0 "out of the box", to read/write from/into it? If not, what would be the "easiest" way to implement this possibility in dom0? Implement a new hypercall which offers this access? I found intresting functions in the public xen-headers (linux like HYPERVISOR_memory_op in include/asm/xen/hypercall.h and the structures xen_memory_exchange or xen_memory_map in memory.h. I'm currently trying to figure out if this is the functionality I'm looking for. Have you any hints for me?


best regards,

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] accessing hvm-domU memory from dom0, david <=