From: Will Deacon <will@kernel.org>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Evgenii Stepanov <eugenis@google.com>,
Peter Collingbourne <pcc@google.com>,
Steven Price <steven.price@arm.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
kasan-dev@googlegroups.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v5] kasan: speed up mte_set_mem_tag_range
Date: Tue, 25 May 2021 19:58:47 +0100 [thread overview]
Message-ID: <162196691854.2317985.15060469643983512129.b4-ty@kernel.org> (raw)
In-Reply-To: <20210521010023.3244784-1-eugenis@google.com>
On Thu, 20 May 2021 18:00:23 -0700, Evgenii Stepanov wrote:
> Use DC GVA / DC GZVA to speed up KASan memory tagging in HW tags mode.
>
> The first cacheline is always tagged using STG/STZG even if the address is
> cacheline-aligned, as benchmarks show it is faster than a conditional
> branch.
Applied to arm64 (for-next/mte), thanks!
[1/1] kasan: speed up mte_set_mem_tag_range
https://git.kernel.org/arm64/c/3d0cca0b02ac
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Evgenii Stepanov <eugenis@google.com>,
Peter Collingbourne <pcc@google.com>,
Steven Price <steven.price@arm.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
kasan-dev@googlegroups.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH v5] kasan: speed up mte_set_mem_tag_range
Date: Tue, 25 May 2021 19:58:47 +0100 [thread overview]
Message-ID: <162196691854.2317985.15060469643983512129.b4-ty@kernel.org> (raw)
In-Reply-To: <20210521010023.3244784-1-eugenis@google.com>
On Thu, 20 May 2021 18:00:23 -0700, Evgenii Stepanov wrote:
> Use DC GVA / DC GZVA to speed up KASan memory tagging in HW tags mode.
>
> The first cacheline is always tagged using STG/STZG even if the address is
> cacheline-aligned, as benchmarks show it is faster than a conditional
> branch.
Applied to arm64 (for-next/mte), thanks!
[1/1] kasan: speed up mte_set_mem_tag_range
https://git.kernel.org/arm64/c/3d0cca0b02ac
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-25 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 1:00 [PATCH v5] kasan: speed up mte_set_mem_tag_range Evgenii Stepanov
2021-05-21 1:00 ` Evgenii Stepanov
2021-05-25 18:58 ` Will Deacon [this message]
2021-05-25 18:58 ` Will Deacon
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=162196691854.2317985.15060469643983512129.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcc@google.com \
--cc=ryabinin.a.a@gmail.com \
--cc=steven.price@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.