From mboxrd@z Thu Jan 1 00:00:00 1970 From: Razvan Cojocaru Subject: Re: RIP register value in p2m_mem_access_check() Date: Wed, 06 Mar 2013 13:35:04 +0200 Message-ID: <513729E8.2060007@gmail.com> References: <5137208F.7000901@gmail.com> <5137335602000078000C3815@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5137335602000078000C3815@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > v->arch.user_regs.eip is what you should look at. It's > expected to be in sync with the VMCS value as long as > nothing (e.g. emulation) modified the value. There's code in > vmx_asm_vmexit_handler to sync the fields, and in > vmx_asm_do_vmentry to sync them back in the opposite > direction. Thank you for your answer. Isn't it possible that emulation is indeed involved, since in p2m_mem_access_check() a page fault has occured, and RIP might point to _after_ the offending instruction? Thanks, Razvan Cojocaru