From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Problems using psr.dd
Date: Thu, 20 Nov 2003 21:24:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106936365907105@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106879020623297@msgid-missing>
>>>>> On Thu, 20 Nov 2003 12:29:42 -0800, "Seth, Rohit" <rohit.seth@intel.com> said:
Rohit> Erratum 11 applies to the cases where rfi is followed by RSE
Rohit> generating instruction in static code stream (i.e. in the
Rohit> source).
Ah, so Keith's interpretation was correct.
Rohit> Have not looked at the Keith's changes but hopefully he has
Rohit> not put any instruction like alloc after rfi in the source.
No, quite the opposite: he put NOPs around it. So clearly this
remains an open issue.
--david
next prev parent reply other threads:[~2003-11-20 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 6:09 Problems using psr.dd Keith Owens
2003-11-20 2:39 ` David Mosberger
2003-11-20 4:32 ` Keith Owens
2003-11-20 7:18 ` Matt Chapman
2003-11-20 7:52 ` Keith Owens
2003-11-20 18:47 ` David Mosberger
2003-11-20 20:29 ` Seth, Rohit
2003-11-20 21:24 ` David Mosberger [this message]
2003-11-20 23:15 ` Keith Owens
2003-11-20 23:32 ` David Mosberger
2003-11-21 0:55 ` Seth, Rohit
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-106936365907105@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