All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	Cornelia Huck <cohuck@redhat.com>,
	Steven Price <steven.price@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	Evgenii Stepanov <eugenis@google.com>
Subject: Re: [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled
Date: Fri, 2 Sep 2022 15:05:23 +0100	[thread overview]
Message-ID: <YxINo9qLJkrVk9/J@arm.com> (raw)
In-Reply-To: <20220810193033.1090251-1-pcc@google.com>

On Wed, Aug 10, 2022 at 12:30:26PM -0700, Peter Collingbourne wrote:
> I rebased Catalin's series onto -next, addressed the issues that I
> identified in the review and added the proposed userspace enablement
> patches after the series.
> 
> [1] https://lore.kernel.org/all/20220705142619.4135905-1-catalin.marinas@arm.com/
> 
> Catalin Marinas (3):
>   arm64: mte: Fix/clarify the PG_mte_tagged semantics
>   KVM: arm64: Simplify the sanitise_mte_tags() logic
>   arm64: mte: Lock a page for MTE tag initialisation
> 
> Peter Collingbourne (4):
>   mm: Add PG_arch_3 page flag

BTW, I rebased these for patches on top of 6.0-rc3 and hopefully
addressed the review comments. I pushed them here:

git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux devel/mte-pg-flags

You may have rebased them already but just in case you haven't, feel
free to pick them up from the above branch.

-- 
Catalin
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Cornelia Huck <cohuck@redhat.com>,
	Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
	Evgenii Stepanov <eugenis@google.com>,
	kvm@vger.kernel.org, Steven Price <steven.price@arm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>
Subject: Re: [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled
Date: Fri, 2 Sep 2022 15:05:23 +0100	[thread overview]
Message-ID: <YxINo9qLJkrVk9/J@arm.com> (raw)
In-Reply-To: <20220810193033.1090251-1-pcc@google.com>

On Wed, Aug 10, 2022 at 12:30:26PM -0700, Peter Collingbourne wrote:
> I rebased Catalin's series onto -next, addressed the issues that I
> identified in the review and added the proposed userspace enablement
> patches after the series.
> 
> [1] https://lore.kernel.org/all/20220705142619.4135905-1-catalin.marinas@arm.com/
> 
> Catalin Marinas (3):
>   arm64: mte: Fix/clarify the PG_mte_tagged semantics
>   KVM: arm64: Simplify the sanitise_mte_tags() logic
>   arm64: mte: Lock a page for MTE tag initialisation
> 
> Peter Collingbourne (4):
>   mm: Add PG_arch_3 page flag

BTW, I rebased these for patches on top of 6.0-rc3 and hopefully
addressed the review comments. I pushed them here:

git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux devel/mte-pg-flags

You may have rebased them already but just in case you haven't, feel
free to pick them up from the above branch.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Collingbourne <pcc@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, Cornelia Huck <cohuck@redhat.com>,
	Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
	Evgenii Stepanov <eugenis@google.com>,
	kvm@vger.kernel.org, Steven Price <steven.price@arm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>
Subject: Re: [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled
Date: Fri, 2 Sep 2022 15:05:23 +0100	[thread overview]
Message-ID: <YxINo9qLJkrVk9/J@arm.com> (raw)
In-Reply-To: <20220810193033.1090251-1-pcc@google.com>

On Wed, Aug 10, 2022 at 12:30:26PM -0700, Peter Collingbourne wrote:
> I rebased Catalin's series onto -next, addressed the issues that I
> identified in the review and added the proposed userspace enablement
> patches after the series.
> 
> [1] https://lore.kernel.org/all/20220705142619.4135905-1-catalin.marinas@arm.com/
> 
> Catalin Marinas (3):
>   arm64: mte: Fix/clarify the PG_mte_tagged semantics
>   KVM: arm64: Simplify the sanitise_mte_tags() logic
>   arm64: mte: Lock a page for MTE tag initialisation
> 
> Peter Collingbourne (4):
>   mm: Add PG_arch_3 page flag

BTW, I rebased these for patches on top of 6.0-rc3 and hopefully
addressed the review comments. I pushed them here:

git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux devel/mte-pg-flags

You may have rebased them already but just in case you haven't, feel
free to pick them up from the above branch.

-- 
Catalin

  parent reply	other threads:[~2022-09-02 14:05 UTC|newest]

Thread overview: 103+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-10 19:30 [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled Peter Collingbourne
2022-08-10 19:30 ` Peter Collingbourne
2022-08-10 19:30 ` Peter Collingbourne
2022-08-10 19:30 ` [PATCH v3 1/7] arm64: mte: Fix/clarify the PG_mte_tagged semantics Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-01 15:49   ` Catalin Marinas
2022-09-01 15:49     ` Catalin Marinas
2022-09-01 15:49     ` Catalin Marinas
2022-09-02 10:26   ` Cornelia Huck
2022-09-02 10:26     ` Cornelia Huck
2022-09-02 10:26     ` Cornelia Huck
2022-09-02 14:47   ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-08-10 19:30 ` [PATCH v3 2/7] KVM: arm64: Simplify the sanitise_mte_tags() logic Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-02 14:47   ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-08-10 19:30 ` [PATCH v3 3/7] mm: Add PG_arch_3 page flag Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-11  7:16   ` kernel test robot
2022-08-11  7:16     ` kernel test robot
2022-08-11  7:16     ` kernel test robot
2022-09-01 17:59     ` Catalin Marinas
2022-09-01 17:59       ` Catalin Marinas
2022-09-01 17:59       ` Catalin Marinas
2022-09-01 17:59       ` Catalin Marinas
2022-09-05 17:01       ` Catalin Marinas
2022-09-05 17:01         ` Catalin Marinas
2022-09-05 17:01         ` Catalin Marinas
2022-09-05 17:01         ` Catalin Marinas
2022-09-19 18:12         ` Marc Zyngier
2022-09-19 18:12           ` Marc Zyngier
2022-09-19 18:12           ` Marc Zyngier
2022-09-19 18:12           ` Marc Zyngier
2022-09-20 15:39           ` Catalin Marinas
2022-09-20 15:39             ` Catalin Marinas
2022-09-20 15:39             ` Catalin Marinas
2022-09-20 15:39             ` Catalin Marinas
2022-09-20 16:33             ` Marc Zyngier
2022-09-20 16:33               ` Marc Zyngier
2022-09-20 16:33               ` Marc Zyngier
2022-09-20 16:33               ` Marc Zyngier
2022-09-20 16:58               ` Catalin Marinas
2022-09-20 16:58                 ` Catalin Marinas
2022-09-20 16:58                 ` Catalin Marinas
2022-09-20 16:58                 ` Catalin Marinas
2022-09-21  3:53                 ` Peter Collingbourne
2022-09-21  3:53                   ` Peter Collingbourne
2022-09-21  3:53                   ` Peter Collingbourne
2022-09-21  3:53                   ` Peter Collingbourne
2022-08-10 19:30 ` [PATCH v3 4/7] arm64: mte: Lock a page for MTE tag initialisation Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-02 14:47   ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-09-02 16:28     ` Catalin Marinas
2022-09-02 16:28       ` Catalin Marinas
2022-09-02 16:28       ` Catalin Marinas
2022-09-02 16:58       ` Catalin Marinas
2022-09-02 16:58         ` Catalin Marinas
2022-09-02 16:58         ` Catalin Marinas
2022-09-05  7:37         ` Steven Price
2022-09-05  7:37           ` Steven Price
2022-09-05  7:37           ` Steven Price
2022-08-10 19:30 ` [PATCH v3 5/7] KVM: arm64: unify the tests for VMAs in memslots when MTE is enabled Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-02 13:41   ` Catalin Marinas
2022-09-02 13:41     ` Catalin Marinas
2022-09-02 13:41     ` Catalin Marinas
2022-09-02 14:47   ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-09-02 14:47     ` Steven Price
2022-08-10 19:30 ` [PATCH v3 6/7] KVM: arm64: permit all VM_MTE_ALLOWED mappings with MTE enabled Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-02 13:45   ` Catalin Marinas
2022-09-02 13:45     ` Catalin Marinas
2022-09-02 13:45     ` Catalin Marinas
2022-09-02 14:47     ` Steven Price
2022-09-02 14:47       ` Steven Price
2022-09-02 14:47       ` Steven Price
2022-09-12 16:23   ` Marc Zyngier
2022-09-12 16:23     ` Marc Zyngier
2022-09-12 16:23     ` Marc Zyngier
2022-09-13  4:10     ` Peter Collingbourne
2022-09-13  4:10       ` Peter Collingbourne
2022-09-13  4:10       ` Peter Collingbourne
2022-08-10 19:30 ` [PATCH v3 7/7] Documentation: document the ABI changes for KVM_CAP_ARM_MTE Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-08-10 19:30   ` Peter Collingbourne
2022-09-02 13:49   ` Catalin Marinas
2022-09-02 13:49     ` Catalin Marinas
2022-09-02 13:49     ` Catalin Marinas
2022-09-02 14:05 ` Catalin Marinas [this message]
2022-09-02 14:05   ` [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled Catalin Marinas
2022-09-02 14:05   ` Catalin Marinas

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=YxINo9qLJkrVk9/J@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=cohuck@redhat.com \
    --cc=eugenis@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=pcc@google.com \
    --cc=steven.price@arm.com \
    --cc=vincenzo.frascino@arm.com \
    --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 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.