All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rzvncj@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: RIP register value in p2m_mem_access_check()
Date: Wed, 06 Mar 2013 15:25:30 +0200	[thread overview]
Message-ID: <513743CA.805@gmail.com> (raw)
In-Reply-To: <5137512C02000078000C394B@nat28.tlf.novell.com>

>> 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?
>
> That wouldn't match your observation (the two values were
> much farther apart), unless a call or jump got emulated.

I've noticed that, and have indeed assumed that it was something like a 
call.

> Further, after emulation, the user_regs.eip value should be the
> canonical one.
>
> And finally, you said you took this right after a page fault
> occurred, and - just like for any fault - the RIP the fault refers
> to is the faulting instruction, not the one following it.

Fair enough. Will debug the issue.


Thanks,
Razvan Cojocaru

  reply	other threads:[~2013-03-06 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 10:55 RIP register value in p2m_mem_access_check() Razvan Cojocaru
2013-03-06 11:15 ` Jan Beulich
2013-03-06 11:35   ` Razvan Cojocaru
2013-03-06 13:22     ` Jan Beulich
2013-03-06 13:25       ` Razvan Cojocaru [this message]
2013-03-06 13:49       ` Razvan Cojocaru
2013-03-06 14:26         ` Razvan Cojocaru
2013-03-06 14:33         ` Jan Beulich
2013-03-06 14:47           ` Razvan Cojocaru
2013-03-07 16:49           ` Tim Deegan
2013-03-07 17:04             ` Jan Beulich
2013-03-07 17:31             ` Razvan Cojocaru

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=513743CA.805@gmail.com \
    --to=rzvncj@gmail.com \
    --cc=JBeulich@suse.com \
    --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.