From: Borislav Petkov <bp@alien8.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
x86@kernel.org, linux-edac@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64
Date: Wed, 3 Jan 2018 13:42:06 +0100 [thread overview]
Message-ID: <20180103124206.sprpyz6lkwvsl7mw@pd.tnic> (raw)
In-Reply-To: <alpine.LRH.2.21.1801031116020.4107@math.ut.ee>
On Wed, Jan 03, 2018 at 11:16:48AM +0200, Meelis Roos wrote:
> ---[ ESPfix Area ]---
> 0xffffff0000000000-0xffffff1800000000 96G pud
> 0xffffff1800000000-0xffffff1800009000 36K pte
> 0xffffff1800009000-0xffffff180000a000 4K ro NX pte
> 0xffffff180000a000-0xffffff1800019000 60K pte
> 0xffffff1800019000-0xffffff180001a000 4K ro NX pte
> 0xffffff180001a000-0xffffff1800029000 60K pte
> 0xffffff1800029000-0xffffff180002a000 4K ro NX pte
> 0xffffff180002a000-0xffffff1800039000 60K pte
> 0xffffff1800039000-0xffffff180003a000 4K ro NX pte
> 0xffffff180003a000-0xffffff1800049000 60K pte
> 0xffffff1800049000-0xffffff180004a000 4K ro NX pte
> 0xffffff180004a000-0xffffff1800059000 60K pte
> 0xffffff1800059000-0xffffff180005a000 4K ro NX pte
> 0xffffff180005a000-0xffffff1800069000 60K pte
> 0xffffff1800069000-0xffffff180006a000 4K ro NX pte
> 0xffffff180006a000-0xffffff1800079000 60K pte
> ... 131059 entries skipped ...
> ---[ High Kernel Mapping ]---
> 0xffffffff80000000-0xffffffff81e00000 30M pmd
> 0xffffffff81e00000-0xffffffff82000000 2M ro PSE GLB x pmd
Ha, this must be it. What I said yesterday about the guard hole
hypervisor range was wrong because we're looking at VA slice [47:12] and
this one matches:
Hex: 0xffffffff81e00000
1111_1111_1111_1111_1111_1111_1111_1111_1000_0001_1110_0000_0000_0000_0000_0000
63 59 55 51 47 43 39 35 31 27 23 19 15 11 7 3
Hex: 0x0000ffff81e000e0
0000_0000_0000_0000_1111_1111_1111_1111_1000_0001_1110_0000_0000_0000_1110_0000
63 59 55 51 47 43 39 35 31 27 23 19 15 11 7 3
So that's at offset 0xe0 in that 2M page in the high kernel mapping.
tglx, ideas?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-01-03 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 20:49 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64 Meelis Roos
2018-01-02 21:27 ` Borislav Petkov
2018-01-02 23:07 ` Thomas Gleixner
2018-01-03 9:16 ` Meelis Roos
2018-01-03 12:42 ` Borislav Petkov [this message]
2018-01-03 13:17 ` Thomas Gleixner
2018-01-03 13:17 ` Thomas Gleixner
2018-01-03 14:01 ` Meelis Roos
2018-01-03 14:01 ` mroos
2018-01-03 16:22 ` [tip:x86/pti] x86/pti: Make sure the user/kernel PTEs match tip-bot for Thomas Gleixner
2018-02-09 23:30 ` Dave Hansen
2018-02-13 15:59 ` Thomas Gleixner
2018-01-03 7:07 ` 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64 Meelis Roos
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=20180103124206.sprpyz6lkwvsl7mw@pd.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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.