linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT pull resend] x86/entry and ras/core
Date: Fri, 12 Jun 2020 22:05:04 -0000	[thread overview]
Message-ID: <159199950433.21782.7922990856385499228.tglx@nanos.tec.linutronix.de> (raw)

[ Resending because it did not make LKML due to header wreckage which my
  sleep deprived and RCU demolished brain did not notice yesterday night and
  my script safety net failed to correct. ]

Linus,

the following two pull requests contain the distangled and rebased
variants of the x86/entry and ras/core branches.

Part 1 is the rebased version of the entry code rework which is based
on

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-2020-06-11

which you merged yesterday. The result is equivalent to the non rebased code
which was in -next up to:

 2823e83a3dc0 ("x86/entry: __always_inline CR2 for noinstr")

On top of that sit 4 smallish fixes for late bug reports including the RCU
mystery which kept Paul and me busy in the last couple of days.

The issue Paul was observing with the latest RCU change in one esoteric
corner case test turned out to be a red herring:

 https://lkml.kernel.org/r/20200612215650.GN4455@paulmck-ThinkPad-P72

Retesting from scratch on the now fully updated x86/entry branch does not
longer show the effect and all tests pass. There is a high propability that
this was a RCU debugging inflicted PEBKAC. Paul claims that this is a
service which RCU provides for free.

Part 2 is the redone ras/core branch which now includes and therefore
depends on x86/entry up to

 f0178fc01fe4 ("x86/entry: Unbreak __irqentry_text_start/end magic")

Omitting the merge was briefly considered, but that would have caused a
tricky merge conflict and a untested rework of

  17fae1294ad9 ("x86/{mce,mm}: Unmap the entire page if the whole page is affected and poisoned")

which already utilizes the sanitized MCE innards. Basically the same
reasoning on the merge decision as a few weeks ago.

The rebase results have been carefully checked, tested and cross diffed to
the extent possible.

Again thanks for your understanding and the exceptional allowance of
rebasing that late.

Thanks,

	Thomas


             reply	other threads:[~2020-06-13 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 22:05 Thomas Gleixner [this message]
2020-06-12 22:05 ` [GIT pull resend] x86/entry for v5.8 Thomas Gleixner
2020-06-13 18:00   ` pr-tracker-bot
2020-07-05  7:12   ` Paolo Bonzini
2020-07-06  9:51     ` Thomas Gleixner
2020-06-12 22:05 ` [GIT pull resend] ras/core " Thomas Gleixner
2020-06-13 18:00   ` pr-tracker-bot

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=159199950433.21782.7922990856385499228.tglx@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --subject='Re: [GIT pull resend] x86/entry and ras/core' \
    /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

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).