From: Big Strong <fangtuo90@gmail.com>
To: xen-devel <xen-devel@lists.xen.org>
Subject: handle virtualization exception
Date: Wed, 1 Jun 2016 11:08:18 +0800 [thread overview]
Message-ID: <CAFnE1f1c_jD1hDshrqCLftTTVm2+4o1+-sVEUDKbDVCdeY1Cig@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 481 bytes --]
Virtualization exception is a fault exception caused by specific type of
EPT violations. The vector is 20, which is not defined in linux kernel
(traps.h), also no exception handling function is defined (traps.c). So is
there any way to implement it as a LKM? As it is needed to
set virtualization-exception information area and virtualization exception
handler ((for example, by executing the EPTP-switching VM function), it is
inflexible to implement it in linux kernel directly.
[-- Attachment #1.2: Type: text/html, Size: 505 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-06-01 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 3:08 Big Strong [this message]
2016-06-04 12:35 ` handle virtualization exception Big Strong
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=CAFnE1f1c_jD1hDshrqCLftTTVm2+4o1+-sVEUDKbDVCdeY1Cig@mail.gmail.com \
--to=fangtuo90@gmail.com \
--cc=xen-devel@lists.xen.org \
/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).