From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Mike <mike.guidry@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Questions regarding XEN subsystems..
Date: Fri, 23 Oct 2015 18:25:39 +0100 [thread overview]
Message-ID: <562A6D93.4030402@citrix.com> (raw)
In-Reply-To: <CAKARBTLtA3GFdnw7_2Aw6bb=Po_hdybX=o21TY9v3DCsODquSw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 909 bytes --]
On 23/10/15 18:16, Mike wrote:
> Hello,
>
> I'm doing some reviewing of XEN source code. Does x86_emulate() (from
> x86_emulate.c) execute on every guest, or is this whenever a machine
> doesn't have hardware assisted virtualization?
By default, guests do not have instructions emulated. They run on the
real hardware.
There are situations which occur, (as a side effect of virtualisation),
when it traps into Xen. e.g. updating pagetables while shadow paging is
in use, a write hitting an MMIO page emulated by Qemu, etc.
In such circumstances, the instruction which faulted must be emulated so
Xen can work out what the guest did, and apply the appropriate action.
e.g. update the pagetable as requested or forward an io request to qemu.
Especially for the SIMD instructions, x86_emulate() is not capable of
providing a software alternative to an instruction not supported by the
hardware.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1609 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-10-23 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 17:16 Questions regarding XEN subsystems Mike
2015-10-23 17:25 ` Andrew Cooper [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=562A6D93.4030402@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=mike.guidry@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 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.