mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carlos López" <clopez@suse.de>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: 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, david@kernel.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: Sun, 15 Nov 2026 23:19:53 +0100	[thread overview]
Message-ID: <749a4a86-5b7e-47ff-a6d8-d885354dc68e@suse.de> (raw)
In-Reply-To: <avd4MOhiTCw0I_e1@gremlin>

On 11/13/26 9:59 PM, Lorenzo Stoakes (ARM) wrote:
> Sorry but as I said to David I really question what you're doing with this
> series on the mm side, and I wonder whether we should even consider it for
> this cycle, frankly, given [0].

I was not aware, sorry. Considering this, I am happy to wait until
7.5-rc1 to send the next version.

> And, myself being the fool who is engaged in the Sisyphean task of
> converting VMA flags everywhere, you can imagine my delight when I saw that
> you (seemingly quite knowingly!) chose to abuse that API, writing code that
> I'll personally have to rewrite later.
> 
> Don't do that please :)

I was also not aware of the ongoing effort, I'll use the new API.

> Please also do not keep respinning based on sashiko feedback. FIRST get a
> clear understanding of what maintainers want.
> 
> Sashiko is a bug finder, not a reviewer.
> 
> And see [1]:
> 
> "Wait for a minimum of one week before resubmitting or pinging reviewers -
> possibly longer during busy times like merge windows."
> 
> Please only respin once a week at the minimum.

Understood. For what it's worth, each version went out about a week
after the previous one, but fair enough, I should have waited for David
and you to agree on direction.

      reply	other threads:[~2026-11-15 22:20 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
2026-11-13 20:59 ` Lorenzo Stoakes (ARM)
2026-11-15 22:19   ` Carlos López [this message]

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=749a4a86-5b7e-47ff-a6d8-d885354dc68e@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®