From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: Re: [PATCH v2] arm: KVM: Fix idmap overlap detection when the kernel is idmap'ed Date: Thu, 25 Aug 2016 20:34:44 +0200 Message-ID: <20160825183444.GA13095@lvm> References: <1471852877-17197-1-git-send-email-marc.zyngier@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu To: Marc Zyngier Return-path: Content-Disposition: inline In-Reply-To: <1471852877-17197-1-git-send-email-marc.zyngier@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org On Mon, Aug 22, 2016 at 09:01:17AM +0100, Marc Zyngier wrote: > We're trying hard to detect when the HYP idmap overlaps with the > HYP va, as it makes the teardown of a cpu dangerous. But there is > one case where an overlap is completely safe, which is when the > whole of the kernel is idmap'ed, which is likely to happen on 32bit > when RAM is at 0x8000000 and we're using a 2G/2G VA split. > > In that case, we can proceed safely. > > Reported-by: Christoffer Dall > Signed-off-by: Marc Zyngier Thanks, applied. -Christoffer