All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rzvncj@gmail.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: Vmx_vmenter_helper() and hvm_inject_page_fault()
Date: Thu, 07 Nov 2013 13:43:47 +0200	[thread overview]
Message-ID: <527B7CF3.70209@gmail.com> (raw)
In-Reply-To: <20131106165325.GB25895@deinos.phlegethon.org>

Hello Tim, thank you for your answer!

> Or, even easier, just leave the EPT state that caused the mem_event in
> the first place -- if the guest retries the instruction it will exit
> again with the same fault and you can have some state in the EPT fault
> handler to say 'next time, inject a pagefault'.

Good suggestion, I'm exploring it as we speak.

But, I would also like to know what the dangers of doing this in the
VMENTRY helper function are. Is it that the VMCS information is not yet
fully there? Is guest_cpu_user_regs() not reliable at that point? What
exactly could go wrong there?

Thanks.

  reply	other threads:[~2013-11-07 11:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  9:31 Vmx_vmenter_helper() and hvm_inject_page_fault() Razvan Cojocaru
2013-11-06  9:49 ` Jan Beulich
     [not found]   ` <CAM-wkEsVZx4AxqYEz5UxuteiMkLNA9Ngq+6dj1bwjA-ZB3rFnQ@mail.gmail.com>
2013-11-06 10:41     ` Fwd: " Razvan Cojocaru
2013-11-06 11:26     ` Jan Beulich
2013-11-06 15:09       ` Razvan Cojocaru
2013-11-06 16:53         ` Tim Deegan
2013-11-07 11:43           ` Razvan Cojocaru [this message]
2013-11-07 19:24             ` Tim Deegan

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=527B7CF3.70209@gmail.com \
    --to=rzvncj@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=tim@xen.org \
    --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.