From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: "Carlos López" <clopez@suse.de>,
kvm@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-riscv@lists.infradead.org, seanjc@google.com,
pbonzini@redhat.com, akpm@linux-foundation.org,
peterx@redhat.com, imbrenda@linux.ibm.com,
borntraeger@linux.ibm.com, frankja@linux.ibm.com,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Subject: Re: [PATCH v3 0/9] KVM: don't zap secondary MMU on permission upgrade
Date: Fri, 13 Nov 2026 20:32:46 +0000 [thread overview]
Message-ID: <avdzWA5nrPLoIztq@gremlin> (raw)
In-Reply-To: <2ff19317-8da9-4014-be04-27fc218b8eea@kernel.org>
On Fri, Nov 13, 2026 at 08:00:02PM +0100, David Hildenbrand (Arm) wrote:
> On 11/12/26 15:20, Carlos López wrote:
> We generally don't add performance improvements without clear motivation and
> data to back it up.
>
> MM is currently busy with more important stuff, so best to keep your changes to
> a bare minimum.
I'm sorry after what I've seen from this series I'm pretty convinced it'd need a
whole bunch of revisions, and we just don't have time for this kind of thing
this cycle.
This is v3 and I already want to NAK it...
--
Cheers, Lorenzo
WARNING: multiple messages have this Message-ID (diff)
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: "Carlos López" <clopez@suse.de>,
kvm@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-riscv@lists.infradead.org, seanjc@google.com,
pbonzini@redhat.com, akpm@linux-foundation.org,
peterx@redhat.com, imbrenda@linux.ibm.com,
borntraeger@linux.ibm.com, frankja@linux.ibm.com,
"Paul Walmsley" <pjw@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Subject: Re: [PATCH v3 0/9] KVM: don't zap secondary MMU on permission upgrade
Date: Fri, 13 Nov 2026 20:32:46 +0000 [thread overview]
Message-ID: <avdzWA5nrPLoIztq@gremlin> (raw)
In-Reply-To: <2ff19317-8da9-4014-be04-27fc218b8eea@kernel.org>
On Fri, Nov 13, 2026 at 08:00:02PM +0100, David Hildenbrand (Arm) wrote:
> On 11/12/26 15:20, Carlos López wrote:
> We generally don't add performance improvements without clear motivation and
> data to back it up.
>
> MM is currently busy with more important stuff, so best to keep your changes to
> a bare minimum.
I'm sorry after what I've seen from this series I'm pretty convinced it'd need a
whole bunch of revisions, and we just don't have time for this kind of thing
this cycle.
This is v3 and I already want to NAK it...
--
Cheers, Lorenzo
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-11-13 20:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 14:20 [PATCH v3 0/9] KVM: don't zap secondary MMU on permission upgrade Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 1/9] mm: fix eager write-bit restore for write-notified shared mappings Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-13 20:47 ` Lorenzo Stoakes (ARM)
2026-11-13 20:47 ` Lorenzo Stoakes (ARM)
2026-11-12 14:20 ` [PATCH v3 2/9] riscv: mm: add pud_soft_dirty() Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-12 14:20 ` [PATCH v3 3/9] mm/huge_memory: honor MM_CP_TRY_CHANGE_WRITABLE in change_huge_pud() Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-13 18:58 ` David Hildenbrand (Arm)
2026-11-13 18:58 ` David Hildenbrand (Arm)
2026-11-13 20:48 ` Lorenzo Stoakes (ARM)
2026-11-13 20:48 ` Lorenzo Stoakes (ARM)
2026-11-12 14:20 ` [PATCH v3 4/9] mm: keep writable entries writable on protection changes Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-13 18:56 ` David Hildenbrand (Arm)
2026-11-13 18:56 ` David Hildenbrand (Arm)
2026-11-12 14:20 ` [PATCH v3 5/9] mm/mprotect: add MM_CP_PERM_UPGRADE Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-13 18:51 ` David Hildenbrand (Arm)
2026-11-13 18:51 ` David Hildenbrand (Arm)
2026-11-13 20:37 ` Lorenzo Stoakes (ARM)
2026-11-13 20:37 ` Lorenzo Stoakes (ARM)
2026-11-12 14:20 ` [PATCH v3 6/9] mm/mmu_notifier: add MMU_NOTIFIER_RANGE_PERM_UPGRADE Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-12 14:20 ` [PATCH v3 7/9] KVM: pass the mmu_notifier event and flags to kvm_gfn_range Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-12 14:20 ` [PATCH v3 8/9] KVM: x86/mmu: don't zap secondary MMU on permission upgrade Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:25 ` sashiko-bot
2026-11-12 14:20 ` [PATCH v3 9/9] KVM: s390: don't unmap the gmap " Carlos López
2026-11-12 14:20 ` Carlos López
2026-11-13 14:26 ` sashiko-bot
2026-11-13 19:00 ` [PATCH v3 0/9] KVM: don't zap secondary MMU " David Hildenbrand (Arm)
2026-11-13 19:00 ` David Hildenbrand (Arm)
2026-11-13 20:32 ` Lorenzo Stoakes (ARM) [this message]
2026-11-13 20:32 ` Lorenzo Stoakes (ARM)
2026-11-13 20:59 ` Lorenzo Stoakes (ARM)
2026-11-13 20:59 ` Lorenzo Stoakes (ARM)
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=avdzWA5nrPLoIztq@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=clopez@suse.de \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=pjw@kernel.org \
--cc=seanjc@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.