From: "Carlos López" <clopez@suse.de>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
kvm@vger.kernel.org, linux-mm@kvack.org
Cc: 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, ljs@kernel.org, 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: Sun, 15 Nov 2026 23:04:54 +0100 [thread overview]
Message-ID: <eabeee00-1ed9-4740-b7b6-6b5be5496766@suse.de> (raw)
In-Reply-To: <2ff19317-8da9-4014-be04-27fc218b8eea@kernel.org>
On 11/13/26 8:00 PM, David Hildenbrand (Arm) wrote:
>> Series overview
>> ===============
>>
>> Patches 1-4 fix cases where change_protection() needlessly makes or
>> leaves entries read-only, so that the next write to them faults. They
>> only affect performance and can be picked up independently.
>
> We generally don't add performance improvements without clear motivation and
> data to back it up.
Right, this is on me for not explaining the dependency better in the
cover letter and the commit messages. Patches 1-4 are required for the
new notifier flag to be correct. I'll explain this better.
> MM is currently busy with more important stuff, so best to keep your changes to
> a bare minimum.
I had not seen your "Firefighting mode" email earlier this week, sorry.
next prev parent reply other threads:[~2026-11-15 22:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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-13 20:47 ` Lorenzo Stoakes (ARM)
2026-11-15 22:00 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 2/9] riscv: mm: add pud_soft_dirty() Carlos López
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-13 18:58 ` David Hildenbrand (Arm)
2026-11-15 22:00 ` Carlos López
2026-11-13 20:48 ` Lorenzo Stoakes (ARM)
2026-11-15 22:00 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 4/9] mm: keep writable entries writable on protection changes Carlos López
2026-11-13 18:56 ` David Hildenbrand (Arm)
2026-11-15 21:59 ` Carlos López
2026-11-12 14:20 ` [PATCH v3 5/9] mm/mprotect: add MM_CP_PERM_UPGRADE Carlos López
2026-11-13 18:51 ` David Hildenbrand (Arm)
2026-11-15 22:03 ` Carlos López
2026-11-13 20:37 ` Lorenzo Stoakes (ARM)
2026-11-15 22:01 ` Carlos López
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 ` [PATCH v3 7/9] KVM: pass the mmu_notifier event and flags to kvm_gfn_range Carlos López
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 ` [PATCH v3 9/9] KVM: s390: don't unmap the gmap " Carlos López
2026-11-13 19:00 ` [PATCH v3 0/9] KVM: don't zap secondary MMU " David Hildenbrand (Arm)
2026-11-13 20:32 ` Lorenzo Stoakes (ARM)
2026-11-15 22:04 ` Carlos López [this message]
2026-11-13 20:59 ` Lorenzo Stoakes (ARM)
2026-11-15 22:19 ` Carlos López
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=eabeee00-1ed9-4740-b7b6-6b5be5496766@suse.de \
--to=clopez@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--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=ljs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®