From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] New rev 2.1 SDM for Itanium published
Date: Fri, 22 Nov 2002 18:27:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805475@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805465@msgid-missing>
>>>>> On Fri, 22 Nov 2002 10:08:39 -0800, "Jim Hull" <jim_hull@hp.com> said:
>> If so, should this be noted somewhere so that naive
>> people who read the manuals don't assume that it's implemented?
Jim> There is a new "ao" bit in CPUID[4], which as described on p. 1:32, will
Jim> be 1 only if the new larger atomic ops are implemented. Do you think
Jim> this is insufficient?
The ao bit seems to have gotten lost in the final version of SDM2.1.
It's mentioned (indirectly) in the Document Revision history, but in
the CPUID[4] description, only "branchlong" and "spontaneous deferral"
show up.
--david
next prev parent reply other threads:[~2002-11-22 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 15:47 [Linux-ia64] New rev 2.1 SDM for Itanium published Mallick, Asit K
2002-11-22 9:12 ` Matt Chapman
2002-11-22 18:08 ` Jim Hull
2002-11-22 18:27 ` David Mosberger [this message]
2002-11-22 19:02 ` Jim Hull
2002-11-22 20:07 ` Bjorn Helgaas
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-105590709805475@msgid-missing \
--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