All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	linux-kselftest@vger.kernel.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Gabor Kertesz <gabor.kertesz@arm.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org,
	Vincenzo Frascino <Vincenzo.Frascino@arm.com>
Subject: Re: [PATCH v2 0/6] kselftest: arm64/mte: Tests for user-space MTE
Date: Mon,  5 Oct 2020 19:08:57 +0100	[thread overview]
Message-ID: <160192033783.52795.7154690742315956684.b4-ty@kernel.org> (raw)
In-Reply-To: <20201002115630.24683-1-amit.kachhap@arm.com>

On Fri, 2 Oct 2020 17:26:24 +0530, Amit Daniel Kachhap wrote:
> These patch series adds below kselftests to test the user-space support for the
> ARMv8.5 Memory Tagging Extension present in arm64 tree [1]. This patch
> series is based on Linux v5.9-rc3.
> 
> 1) This test-case verifies that the memory allocated by kernel mmap interface
> can support tagged memory access. It first checks the presence of tags at
> address[56:59] and then proceeds with read and write. The pass criteria for
> this test is that tag fault exception should not happen.
> 
> [...]

Applied to arm64 (for-next/late-arrivals), thanks!

[1/6] kselftest/arm64: Add utilities and a test to validate mte memory
      https://git.kernel.org/arm64/c/e9b60476bea0
[2/6] kselftest/arm64: Verify mte tag inclusion via prctl
      https://git.kernel.org/arm64/c/f3b2a26ca78d
[3/6] kselftest/arm64: Check forked child mte memory accessibility
      https://git.kernel.org/arm64/c/dfe537cf4718
[4/6] kselftest/arm64: Verify all different mmap MTE options
      https://git.kernel.org/arm64/c/53ec81d23213
[5/6] kselftest/arm64: Verify KSM page merge for MTE pages
      https://git.kernel.org/arm64/c/f981d8fa2646
[6/6] kselftest/arm64: Check mte tagged user address in kernel
      https://git.kernel.org/arm64/c/4dafc08d0ba4

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: linux-arm-kernel@lists.infradead.org,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	linux-kselftest@vger.kernel.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	catalin.marinas@arm.com, Gabor Kertesz <gabor.kertesz@arm.com>,
	linux-kernel@vger.kernel.org,
	Vincenzo Frascino <Vincenzo.Frascino@arm.com>,
	Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2 0/6] kselftest: arm64/mte: Tests for user-space MTE
Date: Mon,  5 Oct 2020 19:08:57 +0100	[thread overview]
Message-ID: <160192033783.52795.7154690742315956684.b4-ty@kernel.org> (raw)
In-Reply-To: <20201002115630.24683-1-amit.kachhap@arm.com>

On Fri, 2 Oct 2020 17:26:24 +0530, Amit Daniel Kachhap wrote:
> These patch series adds below kselftests to test the user-space support for the
> ARMv8.5 Memory Tagging Extension present in arm64 tree [1]. This patch
> series is based on Linux v5.9-rc3.
> 
> 1) This test-case verifies that the memory allocated by kernel mmap interface
> can support tagged memory access. It first checks the presence of tags at
> address[56:59] and then proceeds with read and write. The pass criteria for
> this test is that tag fault exception should not happen.
> 
> [...]

Applied to arm64 (for-next/late-arrivals), thanks!

[1/6] kselftest/arm64: Add utilities and a test to validate mte memory
      https://git.kernel.org/arm64/c/e9b60476bea0
[2/6] kselftest/arm64: Verify mte tag inclusion via prctl
      https://git.kernel.org/arm64/c/f3b2a26ca78d
[3/6] kselftest/arm64: Check forked child mte memory accessibility
      https://git.kernel.org/arm64/c/dfe537cf4718
[4/6] kselftest/arm64: Verify all different mmap MTE options
      https://git.kernel.org/arm64/c/53ec81d23213
[5/6] kselftest/arm64: Verify KSM page merge for MTE pages
      https://git.kernel.org/arm64/c/f981d8fa2646
[6/6] kselftest/arm64: Check mte tagged user address in kernel
      https://git.kernel.org/arm64/c/4dafc08d0ba4

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

  parent reply	other threads:[~2020-10-05 18:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 11:56 [PATCH v2 0/6] kselftest: arm64/mte: Tests for user-space MTE Amit Daniel Kachhap
2020-10-02 11:56 ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 1/6] kselftest/arm64: Add utilities and a test to validate mte memory Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 2/6] kselftest/arm64: Verify mte tag inclusion via prctl Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 3/6] kselftest/arm64: Check forked child mte memory accessibility Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 4/6] kselftest/arm64: Verify all different mmap MTE options Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 5/6] kselftest/arm64: Verify KSM page merge for MTE pages Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 11:56 ` [PATCH v2 6/6] kselftest/arm64: Check mte tagged user address in kernel Amit Daniel Kachhap
2020-10-02 11:56   ` Amit Daniel Kachhap
2020-10-02 18:00 ` [PATCH v2 0/6] kselftest: arm64/mte: Tests for user-space MTE Catalin Marinas
2020-10-02 18:00   ` Catalin Marinas
2020-10-05 18:08 ` Will Deacon [this message]
2020-10-05 18:08   ` 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=160192033783.52795.7154690742315956684.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=Vincenzo.Frascino@arm.com \
    --cc=amit.kachhap@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=gabor.kertesz@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@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 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.