From: Carl Worth <carl@os.amperecomputing.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Taehyun Noh <taehyun@utexas.edu>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, andreyknvl@gmail.com,
pcc@google.com, yeoreum.yun@arm.com
Subject: Re: [PATCH 2/2] arm64: mte: Defer disabling of TCO until user_access_begin/end
Date: Wed, 14 Jan 2026 12:27:35 -0800 [thread overview]
Message-ID: <87bjiw9byg.fsf@rasp.cworth.amperemail.amperecomputing.com> (raw)
In-Reply-To: <aWJN9JvJilmquWlH@arm.com>
Catalin Marinas <catalin.marinas@arm.com> writes:
> On Fri, Jan 09, 2026 at 11:29:29PM -0600, Taehyun Noh wrote:
>> Our team agrees with Catalin’s TCMA1 solution. It disables every kernel
>> tag checking but the user address will get tag checked as far as TCO is
>> clear. Also, Carl’s initial testing confirms that
>> `mem_access_checked*:k` counters drop with the TCMA1 patch. While we
>> haven’t run the memcached benchmark yet, we will follow up with those
>> results shortly.
>
> That's great. Carl, could you please respin the patch with just setting
> the TCMA1 bit? Just add a suggested-by me (I could post the patch as
> well but I don't have the data to back it up and include in the commit
> log).
Will do. I'm just running the final benchmark numbers and then will send
this out.
-Carl
prev parent reply other threads:[~2026-01-14 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 3:49 [PATCH 0/2] arm64: mte: Improve performance by tightening handling of PSTATE.TCO Carl Worth
2025-10-31 3:49 ` [PATCH 1/2] arm64: mte: Unify kernel MTE policy and manipulation of TCO Carl Worth
2026-01-08 15:05 ` Will Deacon
2026-01-08 16:28 ` Yeoreum Yun
2025-10-31 3:49 ` [PATCH 2/2] arm64: mte: Defer disabling of TCO until user_access_begin/end Carl Worth
2026-01-08 15:06 ` Will Deacon
2026-01-08 18:45 ` Catalin Marinas
2026-01-08 23:19 ` Carl Worth
2026-01-09 11:40 ` Will Deacon
2026-01-10 5:29 ` Taehyun Noh
2026-01-10 13:02 ` Catalin Marinas
2026-01-14 20:27 ` Carl Worth [this message]
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=87bjiw9byg.fsf@rasp.cworth.amperemail.amperecomputing.com \
--to=carl@os.amperecomputing.com \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcc@google.com \
--cc=taehyun@utexas.edu \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.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®