xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: [help] rsp in case of interrupt/exception in ring0
Date: Tue, 23 Feb 2010 19:39:57 -0800	[thread overview]
Message-ID: <20100223193957.33c3e13e@mantra.us.oracle.com> (raw)

Hi,

can someone help me understand this.

When a cpu is in hyp code and int/exception comes in, how/where is rsp 
saved? According to intel manual if there's no ring transition, then
the cpu doesn't save ss/rsp. 

Following trail from entry.S to show_registers(), I don't see where
regs->rsp is loaded, yet show_registers() displays it happily.
show_stack() uses it. 

This also means that regs->rsp is actually going
to prev frame where orig hyp function was executing.

thanks,
Mukesh

             reply	other threads:[~2010-02-24  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  3:39 Mukesh Rathor [this message]
2010-02-24  8:35 ` [help] rsp in case of interrupt/exception in ring0 Jan Beulich
2010-02-25  4:42   ` Mukesh Rathor

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=20100223193957.33c3e13e@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=Xen-devel@lists.xensource.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).