All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Failed vm entry with heavy use of emulator
Date: Tue, 5 Jan 2016 14:35:11 +0200	[thread overview]
Message-ID: <568BB87F.7000207@bitdefender.com> (raw)
In-Reply-To: <CABfawh=H7WeZE4+Qise16fOM511ikR5KwNizNksk8qwUnVr_NQ@mail.gmail.com>

On 01/05/2016 01:49 PM, Tamas K Lengyel wrote:
> Hi all,
> I've been stress-testing the built-in emulator using the vm_event
> response VM_EVENT_FLAG_EMULATE feature. In the test I've turned all
> pages non-readable by default and all trapped instructions to be
> emulated. My test code can be found at
> https://github.com/tklengyel/xen/compare/read_emul?expand=1.
> 
> The following crash is reproducible and has been verified by Razvan as well.

Indeed, but I should point out that it only occurs when all the pages
are not readable. For all other cases (restricting write or execute,
that have been heavily tested here) there seem to be no issues,
regardless of how hard we're driving the emulator.

Tamas found this strange (and I agree) since we've assumed that the
emulator doesn't care about EPT restrictions. But our use cases so far
have never blocked page reads.


Cheers,
Razvan

      parent reply	other threads:[~2016-01-05 12:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 11:49 Failed vm entry with heavy use of emulator Tamas K Lengyel
2016-01-05 11:56 ` Andrew Cooper
2016-01-05 12:05   ` Tamas K Lengyel
2016-01-05 13:45     ` Andrew Cooper
2016-01-06 14:21     ` Jan Beulich
2016-01-05 13:39   ` Razvan Cojocaru
2016-01-05 13:49     ` Andrew Cooper
2016-01-05 14:01       ` Razvan Cojocaru
2016-01-05 14:12         ` Andrew Cooper
2016-01-05 14:16         ` Tamas K Lengyel
2016-01-05 14:37           ` Razvan Cojocaru
2016-09-06 23:31             ` Tamas K Lengyel
2016-09-07  5:59               ` Razvan Cojocaru
2016-09-07  9:36                 ` Jan Beulich
2016-01-05 12:35 ` Razvan Cojocaru [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=568BB87F.7000207@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=tamas.k.lengyel@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 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.