All of lore.kernel.org
 help / color / mirror / Atom feed
From: peter.maydell@linaro.org (Peter Maydell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: kvm: define PAGE_S2_DEVICE as read-only by default
Date: Mon, 15 Sep 2014 12:45:46 -0700	[thread overview]
Message-ID: <CAFEAcA9kZve_TRxi_5wjTZ34hG586G4gwV-TaW06K10NLZZvOw@mail.gmail.com> (raw)
In-Reply-To: <541740FF.2080105@samsung.com>

On 15 September 2014 12:41, Mario Smarduch <m.smarduch@samsung.com> wrote:
> I've been working around the edges of this discussion, and
> maybe be little unclear on this.
>
> But the manuals say intersection of Stage1/Stage2 permissions are
> used. If guest sets stage1 to read-only then setting stage 2
> to read-only or read-write should have no impact. So why
> should stage 2 RW be changed?

Read versus read-write isn't relevant. The point is
that you mustn't let the guest set up a Normal memory
mapping of the same bit of hardware (phys. address
space) that some other guest or the host has set up
as Device mapping.

-- PMM

  reply	other threads:[~2014-09-15 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 10:17 [PATCH 1/2] ARM: kvm: define PAGE_S2_DEVICE as read-only by default Ard Biesheuvel
2014-09-13 10:17 ` [PATCH 2/2] arm64: " Ard Biesheuvel
2014-09-13 10:41 ` [PATCH 1/2] ARM: " Marc Zyngier
2014-09-13 11:15   ` Ard Biesheuvel
2014-09-13 17:06     ` Christoffer Dall
2014-09-14  4:49       ` Ard Biesheuvel
2014-09-14  9:09         ` Marc Zyngier
2014-09-14  9:43           ` Ard Biesheuvel
2014-09-14 22:57             ` Ard Biesheuvel
2014-09-15  3:37               ` Peter Maydell
2014-09-15 19:41               ` Mario Smarduch
2014-09-15 19:45                 ` Peter Maydell [this message]
2014-09-17 19:19               ` Mario Smarduch

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=CAFEAcA9kZve_TRxi_5wjTZ34hG586G4gwV-TaW06K10NLZZvOw@mail.gmail.com \
    --to=peter.maydell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.