All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Bernhard Held <berny156@gmx.de>, Toshi Kani <toshi.kani@hp.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Brian Gerst <brgerst@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Andrew Lutomirski <luto@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT
Date: Sun, 28 May 2017 11:43:30 -0700	[thread overview]
Message-ID: <CALCETrVKrpRoCv_4r_DVfwvnFhGRQKrf=tDkGb5+VHp9Ai54Zg@mail.gmail.com> (raw)
In-Reply-To: <3d69fb9d-651a-8266-8e00-789fedd74659@gmx.de>

On Sun, May 28, 2017 at 11:18 AM, Bernhard Held <berny156@gmx.de> wrote:
> Hi,
>
> this patch breaks the boot of my kernel. The last message is "Booting
> the kernel.".
>
> My setup might be unusual: I'm running a Xenon E5450 (LGA 771) in a
> Gigbayte G33-DS3R board (LGA 775). The BIOS is patched with the
> microcode of the E5450 and recognizes the CPU.
>
> Please find below the dmesg of a the latest kernel w/o the PAT-patch.
> I'm happy to provide more information or to test patches.

I think this patch is bogus.  pat_enabled() sure looks like it's
supposed to return true if PAT is *enabled*, and these days PAT is
"enabled" even if there's no HW PAT support.  Even if the patch were
somehow correct, it should have been split up into two patches, one to
change pat_enabled() and one to use this_cpu_has().

Ingo, I'd suggest reverting the patch, cc-ing stable on the revert so
-stable knows not to backport it, and starting over with the fix.
>From very brief inspection, the right fix is to make sure that
pat_init(), or at least init_cache_modes(), gets called on the
affected CPUs.

As a future cleanup, I think that pat_enabled() could be deleted
outright and, if needed, replaced by functions like have_memtype_wc()
or similar.  (Do we already have helpers like that?)  Toshi, am I
right?

--Andy

  reply	other threads:[~2017-05-28 18:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 19:07 [PATCH] X86: don't report PAT on CPUs that don't support it Mikulas Patocka
2017-04-18 19:28 ` H. Peter Anvin
2017-04-18 20:47   ` Mikulas Patocka
2017-05-14 22:07     ` Mikulas Patocka
2017-05-16 13:57 ` H. Peter Anvin
2017-05-16 15:49   ` Mikulas Patocka
2017-05-18  7:17     ` Ingo Molnar
2017-05-24 10:21 ` [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT tip-bot for Mikulas Patocka
2017-05-28 18:18   ` Bernhard Held
2017-05-28 18:43     ` Andy Lutomirski [this message]
2017-05-29 22:50       ` Mikulas Patocka
2017-05-30 17:14         ` Dominik Brodowski
2017-05-30 17:59           ` Mikulas Patocka
2017-05-30 18:47             ` Dominik Brodowski
2017-05-30 19:30             ` Bernhard Held
2017-05-31  9:39             ` Junichi Nomura
2017-06-06 22:49       ` [PATCH v2] X86: don't report PAT on CPUs that don't support it Mikulas Patocka
2017-06-06 22:51         ` Andy Lutomirski
2017-06-06 23:21           ` Mikulas Patocka
2017-06-13 15:54             ` Andy Lutomirski
2017-06-14 20:24               ` Mikulas Patocka
2017-06-07 19:54         ` Bernhard Held
2017-07-03  5:05         ` Mikulas Patocka
2017-07-04 13:41           ` Thomas Gleixner
2017-07-04 13:48             ` Thomas Gleixner
2017-07-04 23:04             ` [PATCH v3] " Mikulas Patocka
2017-07-05  7:03               ` [tip:x86/urgent] x86/mm/pat: Don't " tip-bot for Mikulas Patocka
2017-05-31  0:53 [tip:x86/urgent] x86/PAT: Fix Xorg regression on CPUs that don't support PAT Doug Smythies
2017-06-01  7:49 ` Ian W MORRISON
2017-06-01 14:48   ` Ian W MORRISON
2017-06-02  6:32 Ian W MORRISON

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='CALCETrVKrpRoCv_4r_DVfwvnFhGRQKrf=tDkGb5+VHp9Ai54Zg@mail.gmail.com' \
    --to=luto@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=berny156@gmx.de \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=mingo@kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=toshi.kani@hp.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 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.