xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Kai Luo <kluo@vmware.com>
To: xen-devel@lists.xensource.com
Subject: Question's about to detect unauthorized memory access
Date: Tue, 9 Jul 2013 03:52:55 -0700 (PDT)	[thread overview]
Message-ID: <2095964426.21089493.1373367175480.JavaMail.root@vmware.com> (raw)
In-Reply-To: <1725921008.21075110.1373365505787.JavaMail.root@vmware.com>


[-- Attachment #1.1: Type: text/plain, Size: 668 bytes --]

Hi: 
To detect and handle unauthorized memory map from hvm to dom0,I found xsm can prevent a privileged domain from arbitrarily mapping pages from other domains,however,I try to find whether there is another way. So I try to trap the memory access and compare the page owner whth the accessor, if they are different, somthing must happend and a warning to the administrator will be raised. 
My question is how can I trap the memory access? Is there any other mechanism to detect unauthorized memory map?With EPT/NPT, memory access are so closed to hardware that I don‘t know how should I trap it?Can you give me any suggestion? 
Thank you very much! 
Jone 


[-- Attachment #1.2: Type: text/html, Size: 970 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

       reply	other threads:[~2013-07-09 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1725921008.21075110.1373365505787.JavaMail.root@vmware.com>
2013-07-09 10:52 ` Kai Luo [this message]
     [not found]   ` <CAGU+autBm7-roy3Wscic3Pc_ZxYJk+g4crJEn8AzLEkV-KwCSQ@mail.gmail.com>
2013-07-11 19:08     ` Question's about to detect unauthorized memory access Aravindh Puthiyaparambil (aravindp)

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=2095964426.21089493.1373367175480.JavaMail.root@vmware.com \
    --to=kluo@vmware.com \
    --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).