From: prsriva <prsriva@linux.microsoft.com>
To: Pavel Tatashin <pasha.tatashin@soleen.com>,
James Morse <james.morse@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
jean-philippe@linaro.org, arnd@arndb.de,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
sboyd@kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
takahiro.akashi@linaro.org,
kexec mailing list <kexec@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
zohar@linux.ibm.com,
Masahiro Yamada <yamada.masahiro@socionext.com>,
duwe@lst.de, allison@lohutok.net,
linux-integrity@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
bauerman@linux.ibm.com,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V4 0/2] Add support for arm64 to carry ima measurement
Date: Mon, 21 Oct 2019 10:38:44 -0700 [thread overview]
Message-ID: <11036cd6-2977-5f78-7fe7-1085ba31f005@linux.microsoft.com> (raw)
In-Reply-To: <CA+CK2bBVcE91YbJx1f_BkNqbD03wGLNtyane7PjCnEu8i_cH2Q@mail.gmail.com>
On 10/15/19 11:47 AM, Pavel Tatashin wrote:
>> I think the UEFI persistent-memory-reservations thing is a better fit for this [0][1].
>
> Hi James,
>
> Thank you for your thought. As I understand you propose the to use the
> existing method as such:
> 1. Use the existing kexec ABI to pass reservation from kernel to
> kernel using EFI the same as is done for GICv3 tables.
> 2. Allow this memory to be reservable only during first Linux boot via
> EFI memory reserve
> 3. Allow to have this memory pre-reserved by firmware or to be
> embedded into device tree.
>
> A question I have is how to tell that a reserved region is reserved
> for IMA use. With GICv3 it is done by reading the registers, finding
> the interrupt tables memory, and check that the memory ranges are
> indeed pre-reserved.
>
> Is there a way to name memory with the current ABI that you think is acceptable?
>
> Thank you,
> Pasha
>
Friendly ping.
Thanks,
Prakhar Srivastava
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-21 17:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 0:35 [PATCH V4 0/2] Add support for arm64 to carry ima measurement Prakhar Srivastava
2019-10-11 0:35 ` [PATCH V4 1/2] Add support for arm64 to carry ima measurement log in kexec_file_load Prakhar Srivastava
2019-10-11 0:36 ` [PATCH V4 2/2] update powerpc implementation to call into of_ima* Prakhar Srivastava
2019-10-14 18:02 ` [PATCH V4 0/2] Add support for arm64 to carry ima measurement James Morse
2019-10-15 1:31 ` prsriva
2019-10-15 17:39 ` James Morse
2019-10-15 18:47 ` Pavel Tatashin
2019-10-21 17:38 ` prsriva [this message]
2019-10-25 17:08 ` James Morse
2019-10-15 22:15 ` James Morris
2019-10-16 1:44 ` Mimi Zohar
2019-10-25 17:07 ` James Morse
2019-10-25 17:39 ` Mimi Zohar
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=11036cd6-2977-5f78-7fe7-1085ba31f005@linux.microsoft.com \
--to=prsriva@linux.microsoft.com \
--cc=allison@lohutok.net \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bauerman@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=duwe@lst.de \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pasha.tatashin@soleen.com \
--cc=sboyd@kernel.org \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.com \
--cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).