public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Montecito processor family
Date: Wed, 07 Jun 2006 09:22:21 +0000	[thread overview]
Message-ID: <yq0irnds4ky.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <42ADD890.1010406@free.fr>

>>>>> "Ken" = Chen, Kenneth W <kenneth.w.chen@intel.com> writes:

Ken> I thought the x86 acronym was taken straight out of SDM, refer to
Ken> CPUID instruction detail there. We should do the same on ia64.

Ken> Section 3.1.11 out of SDM volume 1:

Ken> field bit description lb 0 long branch (brl) instructions.  sd 1
Ken> spontaneous deferral ao 2 16-byte atomic operations rv 63:3
Ken> Reserved.

Ken> It's only my wishful thinking. The acronym should be improved a
Ken> bit to be more creative and meaningful in its current form.  Oh
Ken> well.

IMHO single words are much nicer to read than strange letter
combos. If we take this path, could we at least make sure it gets
documented in Documentation/ somewhere?

Thanks,
Jes

      parent reply	other threads:[~2006-06-07  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 19:03 Montecito processor family Menyhart, Zoltan
2005-06-13 19:17 ` Yu, Fenghua
2005-11-09 13:54 ` Takayoshi Kochi
2005-11-09 15:24 ` Matthew Wilcox
2005-11-10  1:50 ` Takayoshi Kochi
2006-06-01  0:03 ` Luck, Tony
2006-06-01  1:20 ` Matthew Wilcox
2006-06-01  3:06 ` Russ Anderson
2006-06-01  3:30 ` Alex Williamson
2006-06-01 16:32 ` Luck, Tony
2006-06-02  6:51 ` dann frazier
2006-06-02 22:18 ` Russ Anderson
2006-06-03 18:43 ` Luck, Tony
2006-06-03 19:23 ` David Mosberger-Tang
2006-06-05 20:37 ` Luck, Tony
2006-06-06 18:04 ` Chen, Kenneth W
2006-06-06 18:16 ` Alex Williamson
2006-06-06 18:59 ` Chen, Kenneth W
2006-06-07  9:22 ` Jes Sorensen [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=yq0irnds4ky.fsf@jaguar.mkp.net \
    --to=jes@sgi.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