From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>, Mike Rapoport <rppt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kvmarm@lists.cs.columbia.edu, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH v2 0/1] arm/arm64: add support for folded p4d page tables
Date: Wed, 22 Jan 2020 18:56:38 +0000 [thread overview]
Message-ID: <cb6357040bd5d9fa061a8d3bd96fb571@kernel.org> (raw)
In-Reply-To: <20200122185017.GA17321@willie-the-truck>
On 2020-01-22 18:50, Will Deacon wrote:
> On Mon, Jan 13, 2020 at 01:13:22PM +0200, Mike Rapoport wrote:
>> From: Mike Rapoport <rppt@linux.ibm.com>
>>
>> This is a part of clean up of the page table manipulation code that
>> aims to
>> remove asm-generic/5level-fixup.h and asm-generic/pgtable-nop4d-hack.h
>>
>> There is a single patch for both arm and arm64 because doing the
>> conversion
>> separately would mean breaking the shared mmu bits in virt/kvm/arm.
>
> Unfortunately, that's going to be really hard to merge, as the two
> architectures are maintained in different trees and the breadth of this
> patch series is likely to lead to conflicts in both.
But maybe this is the reason we've all been waiting for, for which we
sacrifice 32bit KVM host on the altar of progress, and finally move
along.
Will and I are the only known users, and that'd be a good incentive to
experience some if this 64bit goodness... ;-)
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-01-22 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 11:13 [PATCH v2 0/1] arm/arm64: add support for folded p4d page tables Mike Rapoport
2020-01-13 11:13 ` [PATCH v2 1/1] " Mike Rapoport
2020-01-22 18:50 ` [PATCH v2 0/1] " Will Deacon
2020-01-22 18:56 ` Marc Zyngier [this message]
2020-01-24 12:20 ` Quentin Perret
2020-01-24 13:34 ` Marc Zyngier
2020-01-24 14:02 ` Quentin Perret
2020-01-23 11:59 ` Mike Rapoport
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=cb6357040bd5d9fa061a8d3bd96fb571@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).