From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Alan Modra <amodra@gmail.com>, Peter Bergner <bergner@linux.ibm.com>
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
binutils@sourceware.org
Subject: Re: PowerPC POWER10 updates to dcbf, sync and wait instructions
Date: Mon, 18 May 2020 21:04:59 -0500 [thread overview]
Message-ID: <027660ca-38aa-25ca-f09d-f366c7b65d16@linux.ibm.com> (raw)
In-Reply-To: <20200519010456.GI1088@bubble.grove.modra.org>
On 5/18/20 8:04 PM, Alan Modra wrote:
> On Mon, May 18, 2020 at 04:40:24PM -0500, Peter Bergner wrote:
>> On 5/18/20 3:03 PM, Tulio Magno Quites Machado Filho wrote:
>>> Power ISA 3.1 states the following (page 1038):
>>>
>>> The encodings for dcbfps, dcbstps, plwsync, and phwsync were chosen to
>>> enable software developed to control updates to persistent storage on
>>> processors that comply with Version 3.1 and subsequent versions of the
>>> architecture to run compatibly on the POWER9 processor.
>>>
>>> So, I think these instructions should be available on POWER9 too.
>> [snip]
>>> Likewise here.
>>> Power ISA 3.1, page 1087, figure 5 better describes how they're executed on
>>> earlier processors.
>> I don't think this is saying we should enable the new mnemonics on POWER9,
>> but rather if one of these is assembled for POWER10, that they'll run on
>> POWER9 just fine. Ditto for the sync insns.
>>
>> Alan or Bill,
>>
>> How do you read those paragraphs?
> With the same conclusion as you do.
>
Likewise.
prev parent reply other threads:[~2020-05-19 2:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 22:53 Peter Bergner
2020-05-18 2:36 ` Alan Modra
2020-05-18 3:36 ` Peter Bergner
2020-05-18 4:49 ` Alan Modra
2020-05-18 15:02 ` Peter Bergner
2020-05-18 15:45 ` Peter Bergner
2020-05-19 0:55 ` Alan Modra
2020-05-19 23:11 ` Peter Bergner
2020-05-18 20:03 ` Tulio Magno Quites Machado Filho
2020-05-18 21:40 ` Peter Bergner
2020-05-19 1:04 ` Alan Modra
2020-05-19 2:04 ` Bill Schmidt [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=027660ca-38aa-25ca-f09d-f366c7b65d16@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=amodra@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=binutils@sourceware.org \
--cc=tuliom@linux.ibm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).