public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: RSE and incomplete register frame
Date: Wed, 02 Aug 2006 08:17:35 +0000	[thread overview]
Message-ID: <44D05F9F.3070804@hob.de> (raw)

Hi there,

for an IA64 related question I dropped a query to 
ia64-technical@gelato.unsw.edu.au . However there was not really any 
helpful response. So please let me make use of the bigger audience on 
this list. Your comments are all welcome. Thanks.

Here the original text:
Hi,

while developing an instruction set simulator I found the chapter about 
incomplete register frame (ASDM vol. 2) to be inaccurate. It says that 
the incomplete frame becomes complete when RSE.ndirty_words becomes 
non-negative by executing mandatory RSE loads. However, mandatory RSE 
loads are not touching BSPSTORE or the dirty partition. RSE loads are 
extending the clean partition. Furthermore if you consider RSE.BOF to 
end up inside the clean partition after a br.ret or rfi, then BSPSTORE 
is located above BSP. However, the new current frame should be 
considered complete since there are no mandatory RSE loads needed. Given 
this, BSPSTORE should be replaced by RSE.Bspload, which is the true 
criterion for an incomplete register frame.

The practice when dealing with br.ret or rfi seems to be that BSPSTORE 
is forced to BSP when RSE.BOF is updated into the clean partition. 
However, this behavior is lacking documentation in one of the ASDM.

Christian


____________
Virus checked by G DATA AntiVirusKit



             reply	other threads:[~2006-08-02  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02  8:17 Christian Hildner [this message]
2006-08-03  5:41 ` RSE and incomplete register frame Matthew Chapman
2006-08-03  9:09 ` Christian Hildner

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=44D05F9F.3070804@hob.de \
    --to=christian.hildner@hob.de \
    --cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox