From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Rohan McLure <rmclure@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
christophe.leroy@csgroup.eu, linux-mm@kvack.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v12 06/11] mm/page_table_check: Reinstate address parameter in [__]page_table_check_pte_clear()
Date: Wed, 3 Apr 2024 19:46:07 -0400 [thread overview]
Message-ID: <CA+CK2bBomXx-yfJCLsFLwduOu_Payg0y-t8D+nJYX4XEJ4bF0A@mail.gmail.com> (raw)
In-Reply-To: <20240402051154.476244-7-rmclure@linux.ibm.com>
On Tue, Apr 2, 2024 at 1:11 AM Rohan McLure <rmclure@linux.ibm.com> wrote:
>
> This reverts commit aa232204c468 ("mm/page_table_check: remove unused
> parameter in [__]page_table_check_pte_clear").
>
> Reinstate previously unused parameters for the purpose of supporting
> powerpc platforms, as many do not encode user/kernel ownership of the
> page in the pte, but instead in the address of the access.
>
> Signed-off-by: Rohan McLure <rmclure@linux.ibm.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
next prev parent reply other threads:[~2024-04-03 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 5:11 [PATCH v12 00/11] Support page table check PowerPC Rohan McLure
2024-04-02 5:11 ` [PATCH v12 02/11] mm/page_table_check: Reinstate address parameter in [__]page_table_check_pmd_set() Rohan McLure
2024-04-03 23:19 ` Pasha Tatashin
2024-04-02 5:11 ` [PATCH v12 04/11] mm/page_table_check: Reinstate address parameter in [__]page_table_check_pud_clear() Rohan McLure
2024-04-03 23:21 ` Pasha Tatashin
2024-04-02 5:11 ` [PATCH v12 07/11] mm: Provide address parameter to p{te,md,ud}_user_accessible_page() Rohan McLure
2024-04-03 23:48 ` Pasha Tatashin
2024-04-02 5:11 ` [PATCH v12 09/11] poweprc: mm: Implement *_user_accessible_page() for ptes Rohan McLure
2024-04-04 0:00 ` Pasha Tatashin
2024-04-02 5:11 ` [PATCH v12 10/11] powerpc: mm: Use set_pte_at_unchecked() for early-boot / internal usages Rohan McLure
2024-04-04 0:12 ` Pasha Tatashin
2024-04-02 5:11 ` [PATCH v12 11/11] powerpc: mm: Support page table check Rohan McLure
2024-04-04 0:16 ` Pasha Tatashin
[not found] ` <20240402051154.476244-2-rmclure@linux.ibm.com>
2024-04-03 23:17 ` [PATCH v12 01/11] mm/page_table_check: Reinstate address parameter in [__]page_table_check_pud_set() Pasha Tatashin
2024-04-03 23:24 ` [PATCH v12 00/11] Support page table check PowerPC Pasha Tatashin
[not found] ` <20240402051154.476244-6-rmclure@linux.ibm.com>
2024-04-03 23:26 ` [PATCH v12 05/11] mm/page_table_check: Reinstate address parameter in [__]page_table_check_pmd_clear() Pasha Tatashin
[not found] ` <20240402051154.476244-7-rmclure@linux.ibm.com>
2024-04-03 23:46 ` Pasha Tatashin [this message]
[not found] ` <20240402051154.476244-9-rmclure@linux.ibm.com>
2024-04-03 23:55 ` [PATCH v12 08/11] powerpc: mm: Add pud_pfn() stub Pasha Tatashin
2024-06-18 13:09 ` [PATCH v12 00/11] Support page table check PowerPC LEROY Christophe
2024-07-29 8:27 ` Andrew Donnellan
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=CA+CK2bBomXx-yfJCLsFLwduOu_Payg0y-t8D+nJYX4XEJ4bF0A@mail.gmail.com \
--to=pasha.tatashin@soleen.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rmclure@linux.ibm.com \
--cc=x86@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