From: baskov@ispras.ru
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Ard Biesheuvel <ardb@kernel.org>, Peter Jones <pjones@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
bret.barkelew@microsoft.com
Subject: Re: [PATCH RFC v2 0/2] Handle UEFI NX-restricted page tables
Date: Thu, 17 Mar 2022 16:26:28 +0300 [thread overview]
Message-ID: <9b8493626c3c6c0af415e0b277147f9e@ispras.ru> (raw)
In-Reply-To: <20220303204759.GA20294@srcf.ucam.org>
On 2022-03-03 23:47, Matthew Garrett wrote:
>
> Ok. I think this should really go through the UEFI spec process - I
> agree that from a strict interpretation of the spec, what this firmware
> is doing is legitimate, but I don't like having a situation where we
> have to depend on the DXE spec.
>
> How does Windows handle this? Just update the page tables itself for
> any
> regions it needs during boot?
Sorry for delay.
Windows is closed source, so we cannot give guarantees on its
behavior, but this is our belief regarding its behavior.
Added Bret Barkelew (bret.barkelew@microsoft.com)
to the CC-list in case he can add something.
Regarding the spec changes, we agree it is reasonable,
but whether the spec changes or not it will take some time
to update the edk2.
Our first solution was safer in regards to the use of the services,
yet as Ard suggested, using DXE services is much cleaner
as long as it works.
We can post it to edk2-devel, but our opinion
is that these issues are independent.
Thanks,
Baskov Evgeniy
next prev parent reply other threads:[~2022-03-17 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 15:43 [PATCH RFC v2 0/2] Handle UEFI NX-restricted page tables Baskov Evgeniy
2022-02-24 15:43 ` [PATCH RFC v2 1/2] libstub: declare DXE services table Baskov Evgeniy
2022-02-24 15:43 ` [PATCH RFC v2 2/2] libstub: ensure allocated memory to be executable Baskov Evgeniy
2022-02-28 16:45 ` [PATCH RFC v2 0/2] Handle UEFI NX-restricted page tables Ard Biesheuvel
2022-02-28 18:30 ` Matthew Garrett
2022-03-03 13:42 ` baskov
2022-03-03 20:47 ` Matthew Garrett
2022-03-17 13:26 ` baskov [this message]
2022-03-18 16:37 ` Peter Jones
2022-03-24 16:39 ` baskov
2022-03-25 8:06 ` Ard Biesheuvel
2022-04-13 17:50 ` Ard Biesheuvel
2022-03-29 18:47 ` Peter Jones
2022-03-29 18:47 ` [PATCH] x86: Set the NX-compatibility flag in the PE header Peter Jones
2022-04-13 17:48 ` Ard Biesheuvel
2022-03-03 14:15 ` [PATCH RFC v2 0/2] Handle UEFI NX-restricted page tables baskov
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=9b8493626c3c6c0af415e0b277147f9e@ispras.ru \
--to=baskov@ispras.ru \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=bret.barkelew@microsoft.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).