From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Russell Currey <ruscur@russell.cc>, linuxppc-dev@lists.ozlabs.org
Cc: mopsfelder@gmail.com, joel@jms.id.au, npiggin@gmail.com
Subject: Re: [PATCH v2 1/2] powerpc/powernv: Get L1D flush requirements from device-tree
Date: Tue, 24 May 2022 21:09:22 +1000 [thread overview]
Message-ID: <165339056252.1718562.14599568205155142624.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220404101536.104794-1-ruscur@russell.cc>
On Mon, 4 Apr 2022 20:15:35 +1000, Russell Currey wrote:
> The device-tree properties no-need-l1d-flush-msr-pr-1-to-0 and
> no-need-l1d-flush-kernel-on-user-access are the equivalents of
> H_CPU_BEHAV_NO_L1D_FLUSH_ENTRY and H_CPU_BEHAV_NO_L1D_FLUSH_UACCESS
> from the H_GET_CPU_CHARACTERISTICS hcall on pseries respectively.
>
> In commit d02fa40d759f ("powerpc/powernv: Remove POWER9 PVR version
> check for entry and uaccess flushes") the condition for disabling the
> L1D flush on kernel entry and user access was changed from any non-P9
> CPU to only checking P7 and P8. Without the appropriate device-tree
> checks for newer processors on powernv, these flushes are unnecessarily
> enabled on those systems. This patch corrects this.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/powernv: Get L1D flush requirements from device-tree
https://git.kernel.org/powerpc/c/2efee6adb56159288bce9d1ab51fc9056d7007d4
[2/2] powerpc/powernv: Get STF barrier requirements from device-tree
https://git.kernel.org/powerpc/c/d2a3c131981d4498571908df95c3c9393a00adf5
cheers
prev parent reply other threads:[~2022-05-24 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:15 [PATCH v2 1/2] powerpc/powernv: Get L1D flush requirements from device-tree Russell Currey
2022-04-04 10:15 ` [PATCH v2 2/2] powerpc/powernv: Get STF barrier " Russell Currey
2022-04-05 2:49 ` [PATCH v2 1/2] powerpc/powernv: Get L1D flush " Joel Stanley
2022-04-05 6:13 ` Michael Ellerman
2022-04-05 7:20 ` Joel Stanley
2022-04-10 11:16 ` Michael Ellerman
2022-04-05 23:38 ` Russell Currey
2022-05-24 11:09 ` Michael Ellerman [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=165339056252.1718562.14599568205155142624.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mopsfelder@gmail.com \
--cc=npiggin@gmail.com \
--cc=ruscur@russell.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.