linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: KVM: Fix idmap overlap detection when the kernel is idmap'ed
Date: Thu, 25 Aug 2016 20:34:44 +0200	[thread overview]
Message-ID: <20160825183444.GA13095@lvm> (raw)
In-Reply-To: <1471852877-17197-1-git-send-email-marc.zyngier@arm.com>

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 <christoffer.dall@linaro.org>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>

Thanks, applied.

-Christoffer

      reply	other threads:[~2016-08-25 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  8:01 [PATCH v2] arm: KVM: Fix idmap overlap detection when the kernel is idmap'ed Marc Zyngier
2016-08-25 18:34 ` Christoffer Dall [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=20160825183444.GA13095@lvm \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).