From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: flushrs and the backing store
Date: Mon, 10 May 2004 18:22:26 +0000 [thread overview]
Message-ID: <16543.51298.744463.19937@napali.hpl.hp.com> (raw)
In-Reply-To: <20040510175934.51397.qmail@web60008.mail.yahoo.com>
>>>>> On Mon, 10 May 2004 10:59:34 -0700 (PDT), umut aymakoglu <umutaymak@yahoo.com> said:
Umut> Hi - Is there some kind of documentation that talks about what
Umut> registers are saved in the backing store up to the current
Umut> procedure after flushrs instruction and their
Umut> layout/structure?
Sure, the ASDM [1] does. As does my book (with better figures,
IMHO... ;-) But really, it's quite simple: flushrs writes back all
stacked registers in the dirty partition. The backing store format
consists of naturally-aligned 64-word blocks (512 bytes), with the
first 63 words use to store register values and the 64-th word use to
store the NaT bits of the first 63 words.
--david
[1] http://www.intel.com/design/itanium/manuals/iiasdmanual.htm
prev parent reply other threads:[~2004-05-10 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 17:59 flushrs and the backing store umut aymakoglu
2004-05-10 18:22 ` David Mosberger [this message]
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=16543.51298.744463.19937@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--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