All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Nathan Chancellor <nathan@kernel.org>,
	linux-kernel@vger.kernel.org,
	the arch/x86 maintainers <x86@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT PULL] x86/boot enhancements for v6.14
Date: Mon, 27 Jan 2025 16:51:02 +0100	[thread overview]
Message-ID: <Z5erZirOgJVBAJZ9@gmail.com> (raw)
In-Reply-To: <CAMj1kXFOY2eEhTvy5F4MqpuE-HsGObxNJ8egXK=CYfRrH9bwSQ@mail.gmail.com>


* Ard Biesheuvel <ardb@kernel.org> wrote:

> This is another example of a pattern that is simply broken and 
> guaranteed to fail when booting this kernel as a SEV-SNP guest. So I 
> hope we agree that these issues should be detected at build time, and 
> it is only the quality of the diagnostic message that you are 
> objecting to?

And I believe the fact that they are fatal messages is a problem - we 
should initially just emit (informative) warnings.

Note that in the above case 'SEV-SNP guest' is basically support for a 
niche usecase built into the kernel image, and in the vast majority of 
cases the kernel will boot and work just fine. We should not fail the 
build for breakage in a niche usecase, at least initially.

Thanks,

	Ingo

      reply	other threads:[~2025-01-27 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  7:28 [GIT PULL] x86/cleanups for v6.14 Ingo Molnar
2025-01-21  7:34 ` Ingo Molnar
2025-01-21 11:31   ` Borislav Petkov
2025-01-21 19:40 ` pr-tracker-bot
2025-01-21 21:29 ` [GIT PULL] x86/boot enhancements " Ingo Molnar
2025-01-24 14:06   ` pr-tracker-bot
2025-01-27  3:18   ` Linus Torvalds
2025-01-27 10:20     ` [PATCH] Revert "x86/boot: Reject absolute references in .head.text Ingo Molnar
2025-01-27 15:54       ` [GIT PULL] x86 fix Ingo Molnar
2025-01-27 17:10         ` Linus Torvalds
2025-01-28 22:19           ` Ingo Molnar
2025-01-28 22:22             ` Ingo Molnar
2025-01-28 22:39             ` pr-tracker-bot
2025-01-27 10:25     ` [tip: x86/urgent] Revert "x86/boot: Reject absolute references in .head.text" tip-bot2 for Ingo Molnar
2025-01-27 11:12     ` [GIT PULL] x86/boot enhancements for v6.14 Ard Biesheuvel
2025-01-27 15:51       ` Ingo Molnar [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=Z5erZirOgJVBAJZ9@gmail.com \
    --to=mingo@kernel.org \
    --cc=ardb@kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.