All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Yu Zhao <yuzhao@google.com>
Cc: Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Michael Larabel <michael@michaellarabel.com>,
	kvmarm@lists.linux.dev, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-mm@google.com, Andrew Morton <akpm@linux-foundation.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH mm-unstable v1 3/5] kvm/arm64: add kvm_arch_test_clear_young()
Date: Thu, 23 Feb 2023 09:03:08 +0000	[thread overview]
Message-ID: <86a614ycs3.wl-maz@kernel.org> (raw)
In-Reply-To: <CAOUHufbbs2gG+DPvSOw_N_Kx7FWdZvpdJUvLzko-BDQ8vfd6Xg@mail.gmail.com>

On Thu, 23 Feb 2023 03:58:47 +0000,
Yu Zhao <yuzhao@google.com> wrote:
> 
> On Fri, Feb 17, 2023 at 2:00 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On Fri, 17 Feb 2023 04:21:28 +0000,
> > Yu Zhao <yuzhao@google.com> wrote:
> > >
> > > On Thu, Feb 16, 2023 at 9:12 PM Yu Zhao <yuzhao@google.com> wrote:
> > > >
> > > > This patch adds kvm_arch_test_clear_young() for the vast majority of
> > > > VMs that are not pKVM and run on hardware that sets the accessed bit
> > > > in KVM page tables.
> >
> > I'm really interested in how you can back this statement. 90% of the
> > HW I have access to is not FEAT_HWAFDB capable, either because it
> > predates the feature or because the feature is too buggy to be useful.
> 
> This is my expericen too -- most devices are pre v8.2.

And yet you have no issue writing the above. Puzzling.

> 
> > Do you have numbers?
> 
> Let's do a quick market survey by segment. The following only applies
> to ARM CPUs:
> 
> 1. Phones: none of the major Android phone vendors sell phones running
> VMs; no other major Linux phone vendors.

Maybe you should have a reality check and look at what your own
employer is shipping.

> 2. Laptops: only a very limited number of Chromebooks run VMs, namely
> ACRVM. No other major Linux laptop vendors.

Again, your employer disagree.

> 3. Desktops: no major Linux desktop vendors.

My desktop disagree (I send this from my arm64 desktop VM ).

> 4. Embedded/IoT/Router: no major Linux vendors run VMs (Android Auto
> can be a VM guest on QNX host).

This email is brought to you via a router VM on an arm64 box.

> 5. Cloud: this is where the vast majority VMs come from. Among the
> vendors available to the general public, Ampere is the biggest player.
> Here [1] is a list of its customers. The A-bit works well even on its
> EVT products (Neoverse cores).

Just the phone stuff dwarfs the number of cloud hosts.

Hopefully your patches are better than your market analysis...

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Yu Zhao <yuzhao@google.com>
Cc: linux-mm@google.com, kvm@vger.kernel.org,
	Jonathan Corbet <corbet@lwn.net>,
	Michael Larabel <michael@michaellarabel.com>,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	kvmarm@lists.linux.dev, Paolo Bonzini <pbonzini@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH mm-unstable v1 3/5] kvm/arm64: add kvm_arch_test_clear_young()
Date: Thu, 23 Feb 2023 09:03:08 +0000	[thread overview]
Message-ID: <86a614ycs3.wl-maz@kernel.org> (raw)
In-Reply-To: <CAOUHufbbs2gG+DPvSOw_N_Kx7FWdZvpdJUvLzko-BDQ8vfd6Xg@mail.gmail.com>

On Thu, 23 Feb 2023 03:58:47 +0000,
Yu Zhao <yuzhao@google.com> wrote:
> 
> On Fri, Feb 17, 2023 at 2:00 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On Fri, 17 Feb 2023 04:21:28 +0000,
> > Yu Zhao <yuzhao@google.com> wrote:
> > >
> > > On Thu, Feb 16, 2023 at 9:12 PM Yu Zhao <yuzhao@google.com> wrote:
> > > >
> > > > This patch adds kvm_arch_test_clear_young() for the vast majority of
> > > > VMs that are not pKVM and run on hardware that sets the accessed bit
> > > > in KVM page tables.
> >
> > I'm really interested in how you can back this statement. 90% of the
> > HW I have access to is not FEAT_HWAFDB capable, either because it
> > predates the feature or because the feature is too buggy to be useful.
> 
> This is my expericen too -- most devices are pre v8.2.

And yet you have no issue writing the above. Puzzling.

> 
> > Do you have numbers?
> 
> Let's do a quick market survey by segment. The following only applies
> to ARM CPUs:
> 
> 1. Phones: none of the major Android phone vendors sell phones running
> VMs; no other major Linux phone vendors.

Maybe you should have a reality check and look at what your own
employer is shipping.

> 2. Laptops: only a very limited number of Chromebooks run VMs, namely
> ACRVM. No other major Linux laptop vendors.

Again, your employer disagree.

> 3. Desktops: no major Linux desktop vendors.

My desktop disagree (I send this from my arm64 desktop VM ).

> 4. Embedded/IoT/Router: no major Linux vendors run VMs (Android Auto
> can be a VM guest on QNX host).

This email is brought to you via a router VM on an arm64 box.

> 5. Cloud: this is where the vast majority VMs come from. Among the
> vendors available to the general public, Ampere is the biggest player.
> Here [1] is a list of its customers. The A-bit works well even on its
> EVT products (Neoverse cores).

Just the phone stuff dwarfs the number of cloud hosts.

Hopefully your patches are better than your market analysis...

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Yu Zhao <yuzhao@google.com>
Cc: Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Michael Larabel <michael@michaellarabel.com>,
	kvmarm@lists.linux.dev, kvm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-mm@google.com, Andrew Morton <akpm@linux-foundation.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH mm-unstable v1 3/5] kvm/arm64: add kvm_arch_test_clear_young()
Date: Thu, 23 Feb 2023 09:03:08 +0000	[thread overview]
Message-ID: <86a614ycs3.wl-maz@kernel.org> (raw)
In-Reply-To: <CAOUHufbbs2gG+DPvSOw_N_Kx7FWdZvpdJUvLzko-BDQ8vfd6Xg@mail.gmail.com>

On Thu, 23 Feb 2023 03:58:47 +0000,
Yu Zhao <yuzhao@google.com> wrote:
> 
> On Fri, Feb 17, 2023 at 2:00 AM Marc Zyngier <maz@kernel.org> wrote:
> >
> > On Fri, 17 Feb 2023 04:21:28 +0000,
> > Yu Zhao <yuzhao@google.com> wrote:
> > >
> > > On Thu, Feb 16, 2023 at 9:12 PM Yu Zhao <yuzhao@google.com> wrote:
> > > >
> > > > This patch adds kvm_arch_test_clear_young() for the vast majority of
> > > > VMs that are not pKVM and run on hardware that sets the accessed bit
> > > > in KVM page tables.
> >
> > I'm really interested in how you can back this statement. 90% of the
> > HW I have access to is not FEAT_HWAFDB capable, either because it
> > predates the feature or because the feature is too buggy to be useful.
> 
> This is my expericen too -- most devices are pre v8.2.

And yet you have no issue writing the above. Puzzling.

> 
> > Do you have numbers?
> 
> Let's do a quick market survey by segment. The following only applies
> to ARM CPUs:
> 
> 1. Phones: none of the major Android phone vendors sell phones running
> VMs; no other major Linux phone vendors.

Maybe you should have a reality check and look at what your own
employer is shipping.

> 2. Laptops: only a very limited number of Chromebooks run VMs, namely
> ACRVM. No other major Linux laptop vendors.

Again, your employer disagree.

> 3. Desktops: no major Linux desktop vendors.

My desktop disagree (I send this from my arm64 desktop VM ).

> 4. Embedded/IoT/Router: no major Linux vendors run VMs (Android Auto
> can be a VM guest on QNX host).

This email is brought to you via a router VM on an arm64 box.

> 5. Cloud: this is where the vast majority VMs come from. Among the
> vendors available to the general public, Ampere is the biggest player.
> Here [1] is a list of its customers. The A-bit works well even on its
> EVT products (Neoverse cores).

Just the phone stuff dwarfs the number of cloud hosts.

Hopefully your patches are better than your market analysis...

	M.

-- 
Without deviation from the norm, progress is not possible.

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

  reply	other threads:[~2023-02-23  9:03 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  4:12 [PATCH mm-unstable v1 0/5] mm/kvm: lockless accessed bit harvest Yu Zhao
2023-02-17  4:12 ` Yu Zhao
2023-02-17  4:12 ` Yu Zhao
2023-02-17  4:12 ` [PATCH mm-unstable v1 1/5] mm/kvm: add mmu_notifier_test_clear_young() Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-23 17:13   ` Sean Christopherson
2023-02-23 17:13     ` Sean Christopherson
2023-02-23 17:13     ` Sean Christopherson
2023-02-23 17:40     ` Yu Zhao
2023-02-23 17:40       ` Yu Zhao
2023-02-23 17:40       ` Yu Zhao
2023-02-23 21:12       ` Sean Christopherson
2023-02-23 21:12         ` Sean Christopherson
2023-02-23 21:12         ` Sean Christopherson
2023-02-23 17:34   ` Sean Christopherson
2023-02-23 17:34     ` Sean Christopherson
2023-02-23 17:34     ` Sean Christopherson
2023-02-17  4:12 ` [PATCH mm-unstable v1 2/5] kvm/x86: add kvm_arch_test_clear_young() Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:19   ` Yu Zhao
2023-02-17  4:19     ` Yu Zhao
2023-02-17  4:19     ` Yu Zhao
2023-02-17 16:27   ` Sean Christopherson
2023-02-17 16:27     ` Sean Christopherson
2023-02-17 16:27     ` Sean Christopherson
2023-02-23  5:58     ` Yu Zhao
2023-02-23  5:58       ` Yu Zhao
2023-02-23  5:58       ` Yu Zhao
2023-02-23 17:09       ` Sean Christopherson
2023-02-23 17:09         ` Sean Christopherson
2023-02-23 17:09         ` Sean Christopherson
2023-02-23 17:27         ` Yu Zhao
2023-02-23 17:27           ` Yu Zhao
2023-02-23 17:27           ` Yu Zhao
2023-02-23 18:23           ` Sean Christopherson
2023-02-23 18:23             ` Sean Christopherson
2023-02-23 18:23             ` Sean Christopherson
2023-02-23 18:34             ` Yu Zhao
2023-02-23 18:34               ` Yu Zhao
2023-02-23 18:34               ` Yu Zhao
2023-02-23 18:47               ` Sean Christopherson
2023-02-23 18:47                 ` Sean Christopherson
2023-02-23 18:47                 ` Sean Christopherson
2023-02-23 19:02                 ` Yu Zhao
2023-02-23 19:02                   ` Yu Zhao
2023-02-23 19:02                   ` Yu Zhao
2023-02-23 19:21                   ` Sean Christopherson
2023-02-23 19:21                     ` Sean Christopherson
2023-02-23 19:21                     ` Sean Christopherson
2023-02-23 19:25                     ` Yu Zhao
2023-02-23 19:25                       ` Yu Zhao
2023-02-23 19:25                       ` Yu Zhao
2023-02-17  4:12 ` [PATCH mm-unstable v1 3/5] kvm/arm64: " Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:21   ` Yu Zhao
2023-02-17  4:21     ` Yu Zhao
2023-02-17  4:21     ` Yu Zhao
2023-02-17  9:00     ` Marc Zyngier
2023-02-17  9:00       ` Marc Zyngier
2023-02-17  9:00       ` Marc Zyngier
2023-02-23  3:58       ` Yu Zhao
2023-02-23  3:58         ` Yu Zhao
2023-02-23  3:58         ` Yu Zhao
2023-02-23  9:03         ` Marc Zyngier [this message]
2023-02-23  9:03           ` Marc Zyngier
2023-02-23  9:03           ` Marc Zyngier
2023-02-23  9:18           ` Yu Zhao
2023-02-23  9:18             ` Yu Zhao
2023-02-23  9:18             ` Yu Zhao
2023-02-17  9:09   ` Oliver Upton
2023-02-17  9:09     ` Oliver Upton
2023-02-17  9:09     ` Oliver Upton
2023-02-17 16:00     ` Sean Christopherson
2023-02-17 16:00       ` Sean Christopherson
2023-02-17 16:00       ` Sean Christopherson
2023-02-23  5:25       ` Yu Zhao
2023-02-23  5:25         ` Yu Zhao
2023-02-23  5:25         ` Yu Zhao
2023-02-23  4:43     ` Yu Zhao
2023-02-23  4:43       ` Yu Zhao
2023-02-23  4:43       ` Yu Zhao
2023-02-17  4:12 ` [PATCH mm-unstable v1 4/5] kvm/powerpc: " Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:24   ` Yu Zhao
2023-02-17  4:24     ` Yu Zhao
2023-02-17  4:24     ` Yu Zhao
2023-02-17  4:12 ` [PATCH mm-unstable v1 5/5] mm: multi-gen LRU: use mmu_notifier_test_clear_young() Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-17  4:12   ` Yu Zhao
2023-02-23 17:43   ` Sean Christopherson
2023-02-23 17:43     ` Sean Christopherson
2023-02-23 17:43     ` Sean Christopherson
2023-02-23 18:08     ` Yu Zhao
2023-02-23 18:08       ` Yu Zhao
2023-02-23 18:08       ` Yu Zhao
2023-02-23 19:11       ` Sean Christopherson
2023-02-23 19:11         ` Sean Christopherson
2023-02-23 19:11         ` Sean Christopherson
2023-02-23 19:36         ` Yu Zhao
2023-02-23 19:36           ` Yu Zhao
2023-02-23 19:36           ` Yu Zhao
2023-02-23 19:58           ` Sean Christopherson
2023-02-23 19:58             ` Sean Christopherson
2023-02-23 19:58             ` Sean Christopherson
2023-02-23 20:09             ` Yu Zhao
2023-02-23 20:09               ` Yu Zhao
2023-02-23 20:09               ` Yu Zhao
2023-02-23 20:28               ` Sean Christopherson
2023-02-23 20:28                 ` Sean Christopherson
2023-02-23 20:28                 ` Sean Christopherson
2023-02-23 20:48                 ` Yu Zhao
2023-02-23 20:48                   ` Yu Zhao
2023-02-23 20:48                   ` Yu Zhao

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=86a614ycs3.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@google.com \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@michaellarabel.com \
    --cc=pbonzini@redhat.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yuzhao@google.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.