All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Collingbourne <pcc@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: kbuild-all@lists.01.org, kernel test robot <lkp@intel.com>,
	kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	Cornelia Huck <cohuck@redhat.com>,
	Steven Price <steven.price@arm.com>,
	Evgenii Stepanov <eugenis@google.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag
Date: Tue, 20 Sep 2022 20:53:15 -0700	[thread overview]
Message-ID: <CAMn1gO6vhf=xaHreysfwrunAAmV8OwxxtA9qOP0Bq+TkjrJQJg@mail.gmail.com> (raw)
In-Reply-To: <YynxJYrd15aUJsmp@arm.com>

On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote:
> > On Tue, 20 Sep 2022 16:39:47 +0100,
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote:
> > > > On Mon, 05 Sep 2022 18:01:55 +0100,
> > > > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > > Peter, please let me know if you want to pick this series up together
> > > > > with your other KVM patches. Otherwise I can post it separately, it's
> > > > > worth merging it on its own as it clarifies the page flag vs tag setting
> > > > > ordering.
> > > >
> > > > I'm looking at queuing this, but I'm confused by this comment. Do I
> > > > need to pick this as part of the series? Or is this an independent
> > > > thing (my hunch is that it is actually required not to break other
> > > > architectures...).
> > >
> > > This series series (at least the first patches) won't apply cleanly on
> > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I
> > > can repost the whole series but I don't have the setup to test the
> > > MAP_SHARED KVM option (unless Peter plans to post it soon).
> >
> > I don't feel brave enough to take a series affecting all architectures
>
> It shouldn't affect the others, the only change is that PG_arch_2 is now
> only defined for arm64 but no other architecture is using it. The
> problem with loongarch is that it doesn't have enough spare bits in
> page->flags and even without any patches I think it's broken with the
> right value for NR_CPUS.
>
> > so late in the game, and the whole thing had very little arm64
> > exposure. The latest QEMU doesn't seem to work anymore, so I don't
> > have any MTE-capable emulation (and using the FVP remotely is a pain
> > in the proverbial neck).
> >
> > I'll come back to this after the merge window, should Peter decide to
> > respin the series.
>
> It makes sense.

Apologies for the delay, I've now sent out v4 of this series which
includes the patches on your branch.

Peter
_______________________________________________
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: Peter Collingbourne <pcc@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Marc Zyngier <maz@kernel.org>, kernel test robot <lkp@intel.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	kvmarm@lists.cs.columbia.edu, kbuild-all@lists.01.org,
	Cornelia Huck <cohuck@redhat.com>, Will Deacon <will@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 3/7] mm: Add PG_arch_3 page flag
Date: Tue, 20 Sep 2022 20:53:15 -0700	[thread overview]
Message-ID: <CAMn1gO6vhf=xaHreysfwrunAAmV8OwxxtA9qOP0Bq+TkjrJQJg@mail.gmail.com> (raw)
In-Reply-To: <YynxJYrd15aUJsmp@arm.com>

On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote:
> > On Tue, 20 Sep 2022 16:39:47 +0100,
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote:
> > > > On Mon, 05 Sep 2022 18:01:55 +0100,
> > > > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > > Peter, please let me know if you want to pick this series up together
> > > > > with your other KVM patches. Otherwise I can post it separately, it's
> > > > > worth merging it on its own as it clarifies the page flag vs tag setting
> > > > > ordering.
> > > >
> > > > I'm looking at queuing this, but I'm confused by this comment. Do I
> > > > need to pick this as part of the series? Or is this an independent
> > > > thing (my hunch is that it is actually required not to break other
> > > > architectures...).
> > >
> > > This series series (at least the first patches) won't apply cleanly on
> > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I
> > > can repost the whole series but I don't have the setup to test the
> > > MAP_SHARED KVM option (unless Peter plans to post it soon).
> >
> > I don't feel brave enough to take a series affecting all architectures
>
> It shouldn't affect the others, the only change is that PG_arch_2 is now
> only defined for arm64 but no other architecture is using it. The
> problem with loongarch is that it doesn't have enough spare bits in
> page->flags and even without any patches I think it's broken with the
> right value for NR_CPUS.
>
> > so late in the game, and the whole thing had very little arm64
> > exposure. The latest QEMU doesn't seem to work anymore, so I don't
> > have any MTE-capable emulation (and using the FVP remotely is a pain
> > in the proverbial neck).
> >
> > I'll come back to this after the merge window, should Peter decide to
> > respin the series.
>
> It makes sense.

Apologies for the delay, I've now sent out v4 of this series which
includes the patches on your branch.

Peter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Collingbourne <pcc@google.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Marc Zyngier <maz@kernel.org>, kernel test robot <lkp@intel.com>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	kvmarm@lists.cs.columbia.edu,  kbuild-all@lists.01.org,
	Cornelia Huck <cohuck@redhat.com>, Will Deacon <will@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 3/7] mm: Add PG_arch_3 page flag
Date: Tue, 20 Sep 2022 20:53:15 -0700	[thread overview]
Message-ID: <CAMn1gO6vhf=xaHreysfwrunAAmV8OwxxtA9qOP0Bq+TkjrJQJg@mail.gmail.com> (raw)
In-Reply-To: <YynxJYrd15aUJsmp@arm.com>

On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote:
> > On Tue, 20 Sep 2022 16:39:47 +0100,
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote:
> > > > On Mon, 05 Sep 2022 18:01:55 +0100,
> > > > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > > Peter, please let me know if you want to pick this series up together
> > > > > with your other KVM patches. Otherwise I can post it separately, it's
> > > > > worth merging it on its own as it clarifies the page flag vs tag setting
> > > > > ordering.
> > > >
> > > > I'm looking at queuing this, but I'm confused by this comment. Do I
> > > > need to pick this as part of the series? Or is this an independent
> > > > thing (my hunch is that it is actually required not to break other
> > > > architectures...).
> > >
> > > This series series (at least the first patches) won't apply cleanly on
> > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I
> > > can repost the whole series but I don't have the setup to test the
> > > MAP_SHARED KVM option (unless Peter plans to post it soon).
> >
> > I don't feel brave enough to take a series affecting all architectures
>
> It shouldn't affect the others, the only change is that PG_arch_2 is now
> only defined for arm64 but no other architecture is using it. The
> problem with loongarch is that it doesn't have enough spare bits in
> page->flags and even without any patches I think it's broken with the
> right value for NR_CPUS.
>
> > so late in the game, and the whole thing had very little arm64
> > exposure. The latest QEMU doesn't seem to work anymore, so I don't
> > have any MTE-capable emulation (and using the FVP remotely is a pain
> > in the proverbial neck).
> >
> > I'll come back to this after the merge window, should Peter decide to
> > respin the series.
>
> It makes sense.

Apologies for the delay, I've now sent out v4 of this series which
includes the patches on your branch.

Peter

_______________________________________________
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: Peter Collingbourne <pcc@google.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3 3/7] mm: Add PG_arch_3 page flag
Date: Tue, 20 Sep 2022 20:53:15 -0700	[thread overview]
Message-ID: <CAMn1gO6vhf=xaHreysfwrunAAmV8OwxxtA9qOP0Bq+TkjrJQJg@mail.gmail.com> (raw)
In-Reply-To: <YynxJYrd15aUJsmp@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2145 bytes --]

On Tue, Sep 20, 2022 at 9:58 AM Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Tue, Sep 20, 2022 at 05:33:42PM +0100, Marc Zyngier wrote:
> > On Tue, 20 Sep 2022 16:39:47 +0100,
> > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > On Mon, Sep 19, 2022 at 07:12:53PM +0100, Marc Zyngier wrote:
> > > > On Mon, 05 Sep 2022 18:01:55 +0100,
> > > > Catalin Marinas <catalin.marinas@arm.com> wrote:
> > > > > Peter, please let me know if you want to pick this series up together
> > > > > with your other KVM patches. Otherwise I can post it separately, it's
> > > > > worth merging it on its own as it clarifies the page flag vs tag setting
> > > > > ordering.
> > > >
> > > > I'm looking at queuing this, but I'm confused by this comment. Do I
> > > > need to pick this as part of the series? Or is this an independent
> > > > thing (my hunch is that it is actually required not to break other
> > > > architectures...).
> > >
> > > This series series (at least the first patches) won't apply cleanly on
> > > top of 6.0-rc1 and, of course, we shouldn't break other architectures. I
> > > can repost the whole series but I don't have the setup to test the
> > > MAP_SHARED KVM option (unless Peter plans to post it soon).
> >
> > I don't feel brave enough to take a series affecting all architectures
>
> It shouldn't affect the others, the only change is that PG_arch_2 is now
> only defined for arm64 but no other architecture is using it. The
> problem with loongarch is that it doesn't have enough spare bits in
> page->flags and even without any patches I think it's broken with the
> right value for NR_CPUS.
>
> > so late in the game, and the whole thing had very little arm64
> > exposure. The latest QEMU doesn't seem to work anymore, so I don't
> > have any MTE-capable emulation (and using the FVP remotely is a pain
> > in the proverbial neck).
> >
> > I'll come back to this after the merge window, should Peter decide to
> > respin the series.
>
> It makes sense.

Apologies for the delay, I've now sent out v4 of this series which
includes the patches on your branch.

Peter

  reply	other threads:[~2022-09-21  3:53 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 [this message]
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 ` [PATCH v3 0/7] KVM: arm64: permit MAP_SHARED mappings with MTE enabled Catalin Marinas
2022-09-02 14:05   ` 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='CAMn1gO6vhf=xaHreysfwrunAAmV8OwxxtA9qOP0Bq+TkjrJQJg@mail.gmail.com' \
    --to=pcc@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=cohuck@redhat.com \
    --cc=eugenis@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=maz@kernel.org \
    --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.