From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, Paul Durrant <Paul.Durrant@citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>]
Date: Wed, 15 Jun 2016 12:46:19 -0400 [thread overview]
Message-ID: <5761865B.6040808@oracle.com> (raw)
In-Reply-To: <5761963D02000078000F56FF@prv-mh.provo.novell.com>
On 06/15/2016 11:54 AM, Jan Beulich wrote:
>
> Yes, albeit two then isn't enough either if we want to fully address
> the basic issue here: We'd have to latch as many translations as
> there are possibly pages involved in the execution of a single
> instruction.
Re: translations changing under us --- can't they change between guest
issuing two STOS instructions and the emulator picking up the latched
one (from the first instruction) when emulating the second?
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-15 16:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 23:49 Xen-unstable 4.8: HVM domain_crash called from emulate.c:144 RIP: c000:[<000000000000336a>] linux
2016-06-15 8:29 ` Jan Beulich
2016-06-15 8:57 ` Sander Eikelenboom
2016-06-15 9:38 ` Sander Eikelenboom
2016-06-15 10:12 ` Jan Beulich
2016-06-15 12:00 ` Sander Eikelenboom
2016-06-15 12:48 ` Jan Beulich
2016-06-15 13:58 ` Sander Eikelenboom
2016-06-15 14:07 ` Jan Beulich
2016-06-15 14:20 ` Boris Ostrovsky
2016-06-15 14:32 ` Boris Ostrovsky
2016-06-15 14:39 ` Jan Beulich
2016-06-15 14:56 ` Boris Ostrovsky
2016-06-15 15:22 ` Jan Beulich
2016-06-15 15:29 ` Paul Durrant
2016-06-15 15:43 ` Jan Beulich
2016-06-15 15:46 ` Paul Durrant
2016-06-15 15:54 ` Jan Beulich
2016-06-15 16:46 ` Boris Ostrovsky [this message]
2016-06-16 8:03 ` Jan Beulich
2016-06-15 14:35 ` Jan Beulich
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=5761865B.6040808@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=linux@eikelenboom.it \
--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.