From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
x86@kernel.org, linux-doc@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, hpa@zytor.com, corbet@lwn.net,
boris.ostrovsky@oracle.com,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH v5 0/3] x86: make rsdp address accessible via boot params
Date: Wed, 10 Oct 2018 09:19:18 +0200 [thread overview]
Message-ID: <20181010071918.GA103159@gmail.com> (raw)
In-Reply-To: <12afa65a-9e07-bb2c-5621-85074ea37135@suse.com>
* Juergen Gross <jgross@suse.com> wrote:
> You can just dive into the discussion we had back in February:
That was half a year and a thousand commits ago! ;-)
> https://lore.kernel.org/lkml/20180213163244.j2zuxyhs4kbfhwgj@gmail.com/
>
> The scheme I have used in V5 of the series is the one you agreed to use
> back then.
>
> A quick summary of the problem you mentioned:
>
> There are some downstream variants of grub2 with a patch breaking the
> boot protocol by writing garbage past the end of setup_header. Adding
> a new field at the end of setup_header (here: rsdp_address) resulted in
> those grub2 variants clobbering the preset value of 0.
>
> The solution is to let grub2 report back the used boot protocol version
> with setting a flag "I am reporting back my version". The kernel now is
> capable to know which fields of setup_header are known to grub2 and can
> act accordingly.
>
> The related grub2 patch series is under review right now.
Ok, that's reassuring - that's all the context I needed.
Would it help grub2 review+integration if we applied this to -tip and staged
it there until the Grub patches are accepted, or can I consider those changes
as grub2 upstream accepted?
I'd like to help make it happen, let me know what the best route is.
Thanks,
Ingo
next prev parent reply other threads:[~2018-10-10 7:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 6:14 [PATCH v5 0/3] x86: make rsdp address accessible via boot params Juergen Gross
2018-10-10 6:14 ` [PATCH v5 1/3] x86/xen: fix boot loader version reported for pvh guests Juergen Gross
2018-10-10 6:14 ` [PATCH v5 2/3] x86/boot: add acpi rsdp address to setup_header Juergen Gross
2018-11-09 22:23 ` PLEASE REVERT URGENTLY: " H. Peter Anvin
2018-11-10 0:38 ` H. Peter Anvin
2018-11-10 6:26 ` Juergen Gross
2018-11-10 6:32 ` H. Peter Anvin
2018-11-10 7:02 ` Juergen Gross
2018-11-10 7:16 ` H. Peter Anvin
2018-11-10 9:03 ` Juergen Gross
2018-11-11 18:49 ` H. Peter Anvin
2018-11-19 16:48 ` Konrad Rzeszutek Wilk
2018-11-10 15:22 ` Juergen Gross
2018-11-11 23:58 ` hpa
2018-10-10 6:14 ` [PATCH v5 3/3] x86/acpi: take rsdp address for boot params if available Juergen Gross
2018-10-10 6:23 ` [PATCH v5 0/3] x86: make rsdp address accessible via boot params Ingo Molnar
2018-10-10 6:39 ` Juergen Gross
2018-10-10 7:19 ` Ingo Molnar [this message]
2018-10-10 7:28 ` Juergen Gross
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=20181010071918.GA103159@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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).