From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Rich Persaud <persaur@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Johnson, Ethan" <ejohns48@cs.rochester.edu>
Subject: Re: [Xen-devel] More questions about Xen memory layout/usage, access to guest memory
Date: Thu, 22 Aug 2019 23:39:29 +0100 [thread overview]
Message-ID: <74cb4fb4-9983-0000-9dbb-8fc24921a372@citrix.com> (raw)
In-Reply-To: <587225E8-C0DE-40BA-B39E-E30F9CE69B92@gmail.com>
On 22/08/2019 21:57, Rich Persaud wrote:
>> On Aug 22, 2019, at 09:51, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>>
>>> On 22/08/2019 03:06, Johnson, Ethan wrote:
>>>
>>> For HVM, obviously anything that can't be virtualized natively by the
>>> hardware needs to be emulated by Xen/QEMU (since the guest kernel isn't
>>> expected to be cooperative to issue PV hypercalls instead); but I would
>>> expect emulation to be limited to the relatively small subset of the ISA
>>> that VMX/SVM can't natively virtualize. Yet I see that x86_emulate.c
>>> supports emulating just about everything. Under what circumstances does
>>> Xen actually need to put all that emulation code to use?
>> Introspection, as I said earlier, which is potentially any instruction.
> Could introspection-specific emulation code be disabled via KConfig?
Not really.
At the point something has trapped for emulation, we must complete it in
a manner consistent with the x86 architecture, or the guest will crash.
If you don't want emulation from introspection, don't start
introspecting in the first place, at which point guest actions won't
trap in the first place.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-22 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 19:51 [Xen-devel] More questions about Xen memory layout/usage, access to guest memory Johnson, Ethan
2019-08-17 11:04 ` Andrew Cooper
2019-08-22 2:06 ` Johnson, Ethan
2019-08-22 13:51 ` Andrew Cooper
2019-08-22 15:06 ` Rian Quinn
2019-08-22 22:42 ` Andrew Cooper
2019-08-22 17:36 ` Tamas K Lengyel
2019-08-22 22:49 ` Andrew Cooper
2019-08-22 20:57 ` Rich Persaud
2019-08-22 22:39 ` Andrew Cooper [this message]
2019-08-22 23:06 ` Tamas K Lengyel
2019-08-23 0:03 ` Andrew Cooper
2019-08-23 1:12 ` Tamas K Lengyel
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=74cb4fb4-9983-0000-9dbb-8fc24921a372@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ejohns48@cs.rochester.edu \
--cc=persaur@gmail.com \
--cc=xen-devel@lists.xenproject.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).