linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2 v2] ARM: KVM: user_mem_abort: support stage 2 MMIO page mapping
Date: Thu, 26 Jun 2014 09:46:26 +0100	[thread overview]
Message-ID: <20140626084625.GA376@arm.com> (raw)
In-Reply-To: <20140625194551.a6443252bf913023159d25fd@freescale.com>

On Thu, Jun 26, 2014 at 01:45:51AM +0100, Kim Phillips wrote:
> From: Kim Phillips <kim.phillips@linaro.org>
> 
> A userspace process can map device MMIO memory via VFIO or /dev/mem,
> e.g., for platform device passthrough support in QEMU.
> 
> During early development, we found the PAGE_S2 memory type being used
> for MMIO mappings.  This patch corrects that by using the more strongly
> ordered memory type for device MMIO mappings: PAGE_S2_DEVICE.
> 
> Signed-off-by: Kim Phillips <kim.phillips@linaro.org>
> Acked-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
> Hi, here's a v2, upon request:
> 
> - rebased onto today's mainline ToT
> - mmu.o-build tested only (ToT build doesn't complete)
> - made commit text less terse
> - added Christoffer's ack

Thanks for reposting this so quickly!

  Acked-by: Will Deacon <will.deacon@arm.com>

Will

  reply	other threads:[~2014-06-26  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 22:08 [PATCH 1/2] ARM: KVM: Enable the KVM-VFIO device Kim Phillips
2014-03-25 22:08 ` [PATCH 2/2] ARM: KVM: user_mem_abort: support stage 2 MMIO page mapping Kim Phillips
2014-05-06 18:04   ` Christoffer Dall
2014-05-07  9:00     ` Marc Zyngier
2014-05-07 14:55       ` Christoffer Dall
2014-06-24 10:23         ` Will Deacon
2014-06-24 10:39           ` Marc Zyngier
2014-06-26  0:45             ` [PATCH 2/2 v2] " Kim Phillips
2014-06-26  8:46               ` Will Deacon [this message]
2014-06-30  9:08                 ` Christoffer Dall
2014-06-30  9:14                   ` Marc Zyngier

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=20140626084625.GA376@arm.com \
    --to=will.deacon@arm.com \
    --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).