[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240410143020.420cafd47bf8af257b2e647a@linux-foundation.org>
Date: Wed, 10 Apr 2024 14:30:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org, Marc Zyngier
<maz@...nel.org>, Oliver Upton <oliver.upton@...ux.dev>, Tianrui Zhao
<zhaotianrui@...ngson.cn>, Bibo Mao <maobibo@...ngson.cn>, Thomas
Bogendoerfer <tsbogend@...ha.franken.de>, Nicholas Piggin
<npiggin@...il.com>, Anup Patel <anup@...infault.org>, Atish Patra
<atishp@...shpatra.org>, Sean Christopherson <seanjc@...gle.com>, David
Hildenbrand <david@...hat.com>, linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev, loongarch@...ts.linux.dev,
linux-mips@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
kvm-riscv@...ts.infradead.org, linux-mm@...ck.org,
linux-trace-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org
Subject: Re: [PATCH 0/4] KVM, mm: remove the .change_pte() MMU notifier and
set_pte_at_notify()
On Fri, 5 Apr 2024 07:58:11 -0400 Paolo Bonzini <pbonzini@...hat.com> wrote:
> Please review! Also feel free to take the KVM patches through the mm
> tree, as I don't expect any conflicts.
It's mainly a KVM thing and the MM changes are small and simple.
I'd say that the KVM tree would be a better home?
Powered by blists - more mailing lists