From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>, Uros Bizjak <ubizjak@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Dennis Zhou <dennis@kernel.org>, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH v2 0/2] percpu: Add a test case and fix for clang
Date: Wed, 16 Oct 2024 21:23:50 +0300 [thread overview]
Message-ID: <20241016182635.1156168-1-andriy.shevchenko@linux.intel.com> (raw)
Add a test case to percpu to check a corner case with the specific
64-bit unsigned value. This test case shows why the first patch is
done in the way it's done.
The before and after has been tested with binary comparison of
the percpu_test module and runnig it on the real Intel system.
v2:
- updated Subject (Dave)
- added test case
Andy Shevchenko (2):
x86/percpu: Fix clang warning when dealing with unsigned types
percpu: Add a test case for the specific 64-bit value addition
arch/x86/include/asm/percpu.h | 7 ++++---
lib/percpu_test.c | 11 ++++++++++-
2 files changed, 14 insertions(+), 4 deletions(-)
--
2.43.0.rc1.1336.g36b5255a03ac
next reply other threads:[~2024-10-16 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 18:23 Andy Shevchenko [this message]
2024-10-16 18:23 ` [PATCH v2 1/2] x86/percpu: Fix clang warning when dealing with unsigned types Andy Shevchenko
2024-10-16 18:23 ` [PATCH v2 2/2] percpu: Add a test case for the specific 64-bit value addition Andy Shevchenko
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=20241016182635.1156168-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--cc=dave.hansen@linux.intel.com \
--cc=dennis@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=ubizjak@gmail.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