xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: david <david_n@gmx.at>
To: xen-devel@lists.xensource.com
Subject: accessing hvm-domU memory from dom0
Date: Tue, 04 Jan 2011 15:19:02 +0100	[thread overview]
Message-ID: <4D232C56.3030909@gmx.at> (raw)
In-Reply-To: <4D1B8175.9000600@gmx.at>

hi,

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 2.6.32.26) 
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?

thanks,

best regards,
david

      reply	other threads:[~2011-01-04 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 17:23 accessing xen headers from dom0 kernel module david
2010-12-21 10:02 ` Ian Campbell
2010-12-29 18:44   ` david
2011-01-04 14:19     ` david [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D232C56.3030909@gmx.at \
    --to=david_n@gmx.at \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).