From: Kees Cook <kees@kernel.org>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: catalin.marinas@arm.com, will@kernel.org, oleg@redhat.com,
tglx@linutronix.de, peterz@infradead.org, luto@kernel.org,
wad@chromium.org, rostedt@goodmis.org, arnd@arndb.de,
ardb@kernel.org, broonie@kernel.org, mark.rutland@arm.com,
rick.p.edgecombe@intel.com, leobras@redhat.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] arm64: entry: Convert to generic entry
Date: Thu, 27 Jun 2024 10:01:11 -0700 [thread overview]
Message-ID: <202406270958.D73912B@keescook> (raw)
In-Reply-To: <20240627081209.3511918-4-ruanjinjie@huawei.com>
On Thu, Jun 27, 2024 at 04:12:09PM +0800, Jinjie Ruan wrote:
> Tested ok with following test cases on Qemu cortex-a53 and HiSilicon
> Kunpeng-920:
> - Run `perf top` command
> - Switch between different `dynamic preempt` mode
> - Use `pseudo nmi`
> - stress-ng CPU stress test.
I think two other things to test would be the MTE functionality
(especially async mode), and kasan in general.
I've really struggled to get MTE working with qemu, so likely real
hardware would be needed for that... I'm hoping the ARM folks have
access to something that would work well for this. :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-06-27 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 8:12 [PATCH v2 0/3] arm64: entry: Convert to generic entry Jinjie Ruan
2024-06-27 8:12 ` [PATCH v2 1/3] entry: Add some arch funcs to support arm64 to use " Jinjie Ruan
2024-06-27 8:12 ` [PATCH v2 2/3] arm64: Prepare to switch to " Jinjie Ruan
2024-06-27 8:12 ` [PATCH v2 3/3] arm64: entry: Convert " Jinjie Ruan
2024-06-27 17:01 ` Kees Cook [this message]
2024-06-27 17:15 ` Mark Brown
2024-06-27 18:24 ` Kees Cook
2024-06-28 3:20 ` Jinjie Ruan
2024-06-28 7:05 ` Jinjie Ruan
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=202406270958.D73912B@keescook \
--to=kees@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=leobras@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rostedt@goodmis.org \
--cc=ruanjinjie@huawei.com \
--cc=tglx@linutronix.de \
--cc=wad@chromium.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).