From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Nicholas Piggin" <npiggin@gmail.com>,
"Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH] powerpc/64s: remove POWER9 DD1 support
Date: Mon, 11 Jun 2018 12:20:46 +1000 [thread overview]
Message-ID: <cade6efff10d9d016b90536365b2ea89acc9d642.camel@kernel.crashing.org> (raw)
In-Reply-To: <20180611113734.136fce95@roar.ozlabs.ibm.com>
On Mon, 2018-06-11 at 11:37 +1000, Nicholas Piggin wrote:
>
> > > -
> > > /* Perform the acknowledge OS to register cycle. */
> > > ack = be16_to_cpu(__x_readw(__x_tima + TM_SPC_ACK_OS_REG));
> > >
> > > @@ -105,7 +93,7 @@ static void GLUE(X_PFX,source_eoi)(u32 hw_irq,
> > > struct xive_irq_data *xd) *
> > > * For LSIs, using the HW EOI cycle works around a
> > > problem
> > > * on P9 DD1 PHBs where the other ESB accesses don't
> > > work
> > > - * properly.
> > > + * properly. XXX: can this be removed?
> > > */
> > > if (xd->flags & XIVE_IRQ_FLAG_LSI)
> > > __x_readq(__x_eoi_page(xd) +
> >
> > Maybe this should be really removed or the comment changed to why it is
> > still useful?
>
> Good point, I meant to ask Ben about that.
We should just update the comment, the game with PQ bits is not useful
for LSIs are they are automatically re-triggered in HW when still
pending. So even with no errata to work around, it's still the right
thing to do.
Cheers,
Ben.
next prev parent reply other threads:[~2018-06-11 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 13:30 [RFC PATCH] powerpc/64s: remove POWER9 DD1 support Nicholas Piggin
2018-06-10 20:58 ` Michal Suchánek
2018-06-11 1:37 ` Nicholas Piggin
2018-06-11 2:20 ` Benjamin Herrenschmidt [this message]
2018-06-13 3:56 ` Michael Ellerman
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=cade6efff10d9d016b90536365b2ea89acc9d642.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
--cc=npiggin@gmail.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 NNTP newsgroup(s).