From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM
Date: Sun, 7 Sep 2014 12:06:34 +0200 [thread overview]
Message-ID: <CAMJs5B__CFvVHU46_m6H3kNp4rXqQdEZmAP2=j4sCjcJLDG1OA@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu-ph_eRvX=bCcryQHx02fTXcaXeHWxyUeyhbhsD2VJ5gg@mail.gmail.com>
On Sun, Sep 7, 2014 at 11:36 AM, Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> On 26 August 2014 13:43, Christoffer Dall <christoffer.dall@linaro.org> wrote:
>> When userspace loads code and data in a read-only memory regions, KVM
>> needs to be able to handle this on arm and arm64. Specifically this is
>> used when running code directly from a read-only flash device; the
>> common scenario is a UEFI blob loaded with the -bios option in QEMU.
>>
>> Note that the MMIO exit on writes to a read-only memory is ABI and can
>> be used to emulate block-erase style flash devices.
>>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
>
> Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
Thanks!
> Are these on track for 3.18?
>
yes, already in kvmarm/next.
-Christoffer
prev parent reply other threads:[~2014-09-07 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 11:43 [PATCH v3 1/2] KVM: Introduce gfn_to_hva_memslot_prot Christoffer Dall
2014-08-26 11:43 ` [PATCH v3 2/2] arm/arm64: KVM: Support KVM_CAP_READONLY_MEM Christoffer Dall
2014-08-26 15:26 ` Marc Zyngier
2014-09-07 9:36 ` Ard Biesheuvel
2014-09-07 10:06 ` 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='CAMJs5B__CFvVHU46_m6H3kNp4rXqQdEZmAP2=j4sCjcJLDG1OA@mail.gmail.com' \
--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).