From: Heiko Carstens <hca@linux.ibm.com>
To: Mukesh Kumar Chaurasiya <mkchauras@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
catalin.marinas@arm.com, will@kernel.org, mark.rutland@arm.com,
maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
chleroy@kernel.org, ritesh.list@gmail.com, sshegde@linux.ibm.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com, tglx@kernel.org,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, ojeda@kernel.org,
boqun@kernel.org, gary@garyguo.net, bjorn3_gh@protonmail.com,
lossin@kernel.org, a.hindborg@kernel.org, aliceryhl@google.com,
tmgross@umich.edu, dakr@kernel.org, daniel.almeida@collabora.com,
tamird@kernel.org, acourbot@nvidia.com, work@onurozkan.dev,
nathan@kernel.org, ndesaulniers@google.com, morbo@google.com,
justinstitt@google.com, jszhang@kernel.org, japo@linux.ibm.com,
jpoimboe@kernel.org, seanjc@google.com, pmladek@suse.com,
thuth@redhat.com, ynorov@nvidia.com, joelagnelf@nvidia.com,
david@davidgow.net, fujita.tomonori@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC] rust: kernel: Add KUnit tests for ARCH_WARN_ASM bug table emission
Date: Fri, 25 Sep 2026 10:44:21 +0200 [thread overview]
Message-ID: <20260925084421.23528Afe-hca@linux.ibm.com> (raw)
In-Reply-To: <arYWDWmMJgIAt1_W@li-1a3e774c-28e4-11b2-a85c-acc9f2883e29.ibm.com>
On Fri, Sep 25, 2026 at 12:06:28PM +0530, Mukesh Kumar Chaurasiya wrote:
> On Thu, Sep 24, 2026 at 05:13:35PM +0200, Heiko Carstens wrote:
> > On Thu, Sep 24, 2026 at 01:15:57PM +0200, Peter Zijlstra wrote:
> > > Untested thingies for arm64 and s390x.
> > > int is_valid_bugaddr(unsigned long addr)
> > > {
> > > - return 1;
> > > + u16 insn;
> > > +
> > > + if (get_kernel_nofault(insn, (u16 *)addr))
> > > + return 0;
> > > +
> > > + return insn == 0x0001 || insn == 0x000e;
> >
> > I have no idea why anybody wants to do this, but it looks like I'm not
> > alone :) In any case: the check is wrong.
> > s390 uses only the monitor call instruction and this should be
> >
> > return insn == 0xaf00;
>
> should i send this out along with ppc. I am not paricularly very good
> with s390's assembly, but if this looks correct to you, i can send it
> out.
No, I still don't get what this fixes, or what the improvement would be
(also not after reading you reply to Mark). The current code is fine for
s390. Unless there is a pressing need I'd like to keep it as it is.
next prev parent reply other threads:[~2026-09-25 8:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 5:50 Mukesh Kumar Chaurasiya (IBM)
2026-09-22 6:47 ` Peter Zijlstra
2026-09-23 6:28 ` Mukesh Kumar Chaurasiya
2026-09-24 11:15 ` Peter Zijlstra
2026-09-24 12:46 ` Mark Rutland
2026-09-24 12:52 ` Peter Zijlstra
2026-09-24 13:05 ` Mark Rutland
2026-09-25 6:32 ` Mukesh Kumar Chaurasiya
2026-09-24 15:13 ` Heiko Carstens
2026-09-25 6:36 ` Mukesh Kumar Chaurasiya
2026-09-25 8:44 ` Heiko Carstens [this message]
2026-09-25 6:38 ` Mukesh Kumar Chaurasiya
2026-09-24 12:31 ` Mark Rutland
2026-09-25 6:21 ` Mukesh Kumar Chaurasiya
2026-09-25 8:06 ` Mark Rutland
2026-09-24 13:00 ` Christophe Leroy (CS GROUP)
2026-09-25 6:34 ` Mukesh Kumar Chaurasiya
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=20260925084421.23528Afe-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=agordeev@linux.ibm.com \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chleroy@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@davidgow.net \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gor@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=japo@linux.ibm.com \
--cc=joelagnelf@nvidia.com \
--cc=jpoimboe@kernel.org \
--cc=jszhang@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mkchauras@gmail.com \
--cc=morbo@google.com \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=pmladek@suse.com \
--cc=ritesh.list@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=seanjc@google.com \
--cc=sshegde@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
--cc=work@onurozkan.dev \
--cc=x86@kernel.org \
--cc=ynorov@nvidia.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
all inboxes | Powered by JetHome®