From: George Shuklin <george.shuklin@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Running domU in ring 2
Date: Mon, 12 Dec 2011 03:43:24 +0400 [thread overview]
Message-ID: <4EE5401C.9050702@gmail.com> (raw)
In-Reply-To: <63429.71.199.121.110.1323642496.squirrel@webmail.cs.cmu.edu>
Where is your ring 2 in x86_64 architecture? They killed It!
On 12.12.2011 02:28, Olatunji Ruwase wrote:
> Hello,
> I am curious as to whether it is possible/practical to run a PV driver
> domain in the x86 protection ring 2 as opposed to ring 1. I m working on
> using hardware logging to capture instruction-grained traces of
> kernel-mode device drivers. My implementation is based on running Xen 3.3
> on Simics simulated hardware. Distinguishing the kernel-mode executions
> of the dom0 and domU (driver domain) in the simulation framework will be
> easier if the kernels ran in different rings, dom0 in ring 1 and domU in
> ring 2.
>
> Thanks,
>
> tunji
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-12-11 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 22:28 Running domU in ring 2 Olatunji Ruwase
2011-12-11 23:43 ` George Shuklin [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=4EE5401C.9050702@gmail.com \
--to=george.shuklin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.