LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sayali Patil <sayalip@linux.ibm.com>
To: kees@kernel.org, Michael Ellerman <mpe@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Ritesh Harjani <ritesh.list@gmail.com>,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>,
	maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 0/2] LKDTM powerpc enhancements - Part2
Date: Wed, 20 May 2026 11:59:35 +0530	[thread overview]
Message-ID: <e683540e-3875-4b7f-ac25-c30ae3d2fc0e@linux.ibm.com> (raw)
In-Reply-To: <fc776993-1ad7-49fd-834e-c1945da28ad9@kernel.org>



On 18/05/26 17:28, Michael Ellerman wrote:
> On 18/5/2026 16:56, Sayali Patil wrote:
>> Hi all,
>>
>> This series adds a new LKDTM trigger PPC_RADIX_TLBIEL, to validate
>> machine check handling on radix MMU systems and improves reliability of
>> the PPC_SLB_MULTIHIT test by adding isync instructions after slbmte
>> operations.
>>
>> Please review the patches and provide any feedback or suggestions
>> for improvement.
>>
>> Thanks,
>> Sayali
>>
>> ---
>>
>> v1->v2
>>   - Split the patch series into two parts.
>>   - Updated "lkdtm/powerpc: add PPC_RADIX_TLBIEL test for radix MCE
>>     validation" as per review comments:
>>     Wrapped Hash-MMU specific functions with #ifdef 
>> CONFIG_PPC_64S_HASH_MMU.
>>     Guarded powerpc_crashtypes registration with #ifdef 
>> CONFIG_PPC_BOOK3S_64
>>     Updated comment explaining the MCE trigger condition for radix MMU.
>>
>> v1: https://lore.kernel.org/all/ 
>> cover.1778057685.git.sayalip@linux.ibm.com/
>> ---
>>
>> Sayali Patil (2):
>>    lkdtm/powerpc: add isync after slbmte to enforce SLB update ordering
>>    lkdtm/powerpc: add PPC_RADIX_TLBIEL test for radix MCE validation
>>
>>   drivers/misc/lkdtm/Makefile             |  2 +-
>>   drivers/misc/lkdtm/core.c               |  2 +-
>>   drivers/misc/lkdtm/powerpc.c            | 49 +++++++++++++++++++++++++
>>   tools/testing/selftests/lkdtm/tests.txt |  1 +
>>   4 files changed, 52 insertions(+), 2 deletions(-)
> 
> Both changes look good to me.
> 
> You should send them to Kees, who maintains lkdtm. I've added him to Cc, 
> but that may not be sufficient to get his attention.
> 
> Reviewed-by: Michael Ellerman <mpe@kernel.org>
> 
> cheers
> 
Thanks for the review, Michael!

Hi Kees,

Could you please review these patches and let me know if you have any 
comments?

Thanks,
Sayali


  reply	other threads:[~2026-05-20  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  6:56 [PATCH v2 0/2] LKDTM powerpc enhancements - Part2 Sayali Patil
2026-05-18  6:56 ` [PATCH v2 1/2] lkdtm/powerpc: add isync after slbmte to enforce SLB update ordering Sayali Patil
2026-05-19  2:24   ` Ritesh Harjani
2026-05-18  6:56 ` [PATCH v2 2/2] lkdtm/powerpc: add PPC_RADIX_TLBIEL test for radix MCE validation Sayali Patil
2026-05-19  2:49   ` Ritesh Harjani
2026-05-18 11:58 ` [PATCH v2 0/2] LKDTM powerpc enhancements - Part2 Michael Ellerman
2026-05-20  6:29   ` Sayali Patil [this message]
2026-05-21 10:21 ` Kees Cook

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=e683540e-3875-4b7f-ac25-c30ae3d2fc0e@linux.ibm.com \
    --to=sayalip@linux.ibm.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@kernel.org \
    --cc=ritesh.list@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