public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Chapman <matthewc@cse.unsw.edu.au>
To: linux-ia64@vger.kernel.org
Subject: Re: Update to Itanium Software Developer's Manual released
Date: Sat, 15 Nov 2003 04:36:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106887104606023@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106883810409669@msgid-missing>

Hi Tony,

I reported this around a year ago but it doesn't seem to have made it
into the SDM or the updates - maybe you can pass it on to the right
people.

I think the documentation for the "tak" instruction is misleading
and should be clarified.  It says:

  Translation Access Key
  Format:      (qp) tak r1 = r3
  Description: The protection key for a given virtual address is
  obtained and placed in GR r1.
  [...]
  GR[r1] = tlb_access_key(GR[r3], itype);

This suggests that you get the protection key in r1, whereas what
you actually get is the protection key shifted left by 8 bits (so
it lines up with where it is in the TLB and PKR insertion formats).

Matt


On Fri, Nov 14, 2003 at 11:27:10AM -0800, Luck, Tony wrote:
> This specification update contains updates to the Intel?
> Itanium? Architecture Software Developer's Manual, Volume
> 1-3. This document is a compilation of specification changes,
> specification clarifications, and documentation changes.
> This document does not cover errata descriptions.
> 
> Download from:
> 
> http://developer.intel.com/design/itanium/downloads/248699.htm
> 
> -Tony Luck
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2003-11-15  4:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 19:27 Update to Itanium Software Developer's Manual released Luck, Tony
2003-11-15  4:36 ` Matt Chapman [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=marc-linux-ia64-106887104606023@msgid-missing \
    --to=matthewc@cse.unsw.edu.au \
    --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