From: Matt Fleming <matt@console-pimps.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: leif.lindholm@linaro.org, roy.franz@linaro.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
msalter@redhat.com, dyoung@redhat.com, linux-efi@vger.kernel.org,
matt.fleming@intel.com, will.deacon@arm.com,
catalin.marinas@arm.com, grant.likely@linaro.org,
geoff.levand@linaro.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@alien8.de>, Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH v3 03/13] arm64: improve CONFIG_STRICT_DEVMEM handling
Date: Tue, 25 Nov 2014 17:39:25 +0000 [thread overview]
Message-ID: <20141125173925.GE3331@console-pimps.org> (raw)
In-Reply-To: <1416315432-8534-4-git-send-email-ard.biesheuvel@linaro.org>
On Tue, 18 Nov, at 01:57:02PM, Ard Biesheuvel wrote:
> Improve the handling of /dev/mem mappings under CONFIG_STRICT_DEVMEM by:
> - allowing read-only access to parts of System RAM that are not
> considered memory by the kernel, this is mainly intended for exposing
> UEFI Configuration tables to userland;
> - avoid using non-cached mappings for those parts of System RAM, as it
> may result in mismatched attributes.
Is this really the best way to expose EFI config tables?
We already have parts in /sys/firmware/efi/ and in particular we expose
the runtime mappings there for kexec on x86.
Hooking this into the /dev/mem infrastructure just seems wrong to me.
--
Matt Fleming, Intel Open Source Technology Center
next parent reply other threads:[~2014-11-25 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1416315432-8534-1-git-send-email-ard.biesheuvel@linaro.org>
[not found] ` <1416315432-8534-4-git-send-email-ard.biesheuvel@linaro.org>
2014-11-25 17:39 ` Matt Fleming [this message]
2014-11-25 17:48 ` [PATCH v3 03/13] arm64: improve CONFIG_STRICT_DEVMEM handling Borislav Petkov
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=20141125173925.GE3331@console-pimps.org \
--to=matt@console-pimps.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dyoung@redhat.com \
--cc=geoff.levand@linaro.org \
--cc=grant.likely@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt.fleming@intel.com \
--cc=msalter@redhat.com \
--cc=pjones@redhat.com \
--cc=roy.franz@linaro.org \
--cc=will.deacon@arm.com \
/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