From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v4] x86/power: Fix 'nosmt' vs. hibernation triple fault during resume
Date: Fri, 31 May 2019 00:14:56 -0500 [thread overview]
Message-ID: <20190531051456.fzkvn62qlkf6wqra@treble> (raw)
In-Reply-To: <nycvar.YFH.7.76.1905310139380.1962@cbobk.fhfr.pm>
On Fri, May 31, 2019 at 01:42:02AM +0200, Jiri Kosina wrote:
> On Thu, 30 May 2019, Josh Poimboeuf wrote:
>
> > > > Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
> > >
> > > Yes, it is, thanks!
> >
> > I still think changing monitor/mwait to use a fixmap address would be a
> > much cleaner way to fix this. I can try to work up a patch tomorrow.
>
> I disagree with that from the backwards compatibility point of view.
>
> I personally am quite frequently using differnet combinations of
> resumer/resumee kernels, and I've never been biten by it so far. I'd guess
> I am not the only one.
> Fixmap sort of breaks that invariant.
Right now there is no backwards compatibility because nosmt resume is
already broken.
For "future" backwards compatibility we could just define a hard-coded
reserved fixmap page address, adjacent to the vsyscall reserved address.
Something like this (not yet tested)? Maybe we could also remove the
resume_play_dead() hack?
diff --git a/arch/x86/include/asm/fixmap.h b/arch/x86/include/asm/fixmap.h
index 9da8cccdf3fb..1c328624162c 100644
--- a/arch/x86/include/asm/fixmap.h
+++ b/arch/x86/include/asm/fixmap.h
@@ -80,6 +80,7 @@ enum fixed_addresses {
#ifdef CONFIG_X86_VSYSCALL_EMULATION
VSYSCALL_PAGE = (FIXADDR_TOP - VSYSCALL_ADDR) >> PAGE_SHIFT,
#endif
+ FIX_MWAIT = (FIXADDR_TOP - VSYSCALL_ADDR - 1) >> PAGE_SHIFT,
#endif
FIX_DBGP_BASE,
FIX_EARLYCON_MEM_BASE,
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 73e69aaaa117..9804fbe25d03 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -108,6 +108,8 @@ int __read_mostly __max_smt_threads = 1;
/* Flag to indicate if a complete sched domain rebuild is required */
bool x86_topology_update;
+static char __mwait_page[PAGE_SIZE];
+
int arch_update_cpu_topology(void)
{
int retval = x86_topology_update;
@@ -1319,6 +1321,8 @@ void __init native_smp_prepare_cpus(unsigned int max_cpus)
smp_quirk_init_udelay();
speculative_store_bypass_ht_init();
+
+ set_fixmap(FIX_MWAIT, __pa_symbol(&__mwait_page));
}
void arch_enable_nonboot_cpus_begin(void)
@@ -1631,11 +1635,12 @@ static inline void mwait_play_dead(void)
}
/*
- * This should be a memory location in a cache line which is
- * unlikely to be touched by other processors. The actual
- * content is immaterial as it is not actually modified in any way.
+ * This memory location is never actually written to. It's mapped at a
+ * reserved fixmap address to ensure the monitored address remains
+ * valid across a hibernation resume operation. Otherwise a triple
+ * fault can occur.
*/
- mwait_ptr = ¤t_thread_info()->flags;
+ mwait_ptr = (void *)fix_to_virt(FIX_MWAIT);
wbinvd();
next prev parent reply other threads:[~2019-05-31 5:15 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 21:31 [PATCH] x86/power: Fix 'nosmt' vs. hibernation triple fault during resume Jiri Kosina
2019-05-29 8:06 ` Rafael J. Wysocki
2019-05-29 9:03 ` Peter Zijlstra
2019-05-29 10:32 ` [PATCH v2] " Jiri Kosina
2019-05-29 12:02 ` Peter Zijlstra
2019-05-29 16:10 ` Josh Poimboeuf
2019-05-29 16:26 ` Jiri Kosina
2019-05-29 17:00 ` Peter Zijlstra
2019-05-29 17:15 ` Thomas Gleixner
2019-05-29 17:17 ` Josh Poimboeuf
2019-05-29 17:29 ` Jiri Kosina
2019-05-29 18:02 ` Jiri Kosina
2019-05-29 20:26 ` [PATCH v3] " Jiri Kosina
2019-05-29 21:25 ` Pavel Machek
2019-05-29 21:27 ` Jiri Kosina
2019-05-29 21:53 ` Pavel Machek
2019-05-29 22:09 ` [PATCH v4] " Jiri Kosina
2019-05-30 8:46 ` Rafael J. Wysocki
2019-05-30 21:27 ` Thomas Gleixner
2019-05-30 21:38 ` Rafael J. Wysocki
2019-05-30 23:38 ` Josh Poimboeuf
2019-05-30 23:42 ` Jiri Kosina
2019-05-31 5:14 ` Josh Poimboeuf [this message]
2019-05-31 8:26 ` Rafael J. Wysocki
2019-05-31 8:47 ` Jiri Kosina
2019-05-31 8:57 ` Rafael J. Wysocki
2019-05-31 14:24 ` Andy Lutomirski
2019-05-31 14:31 ` Jiri Kosina
2019-05-31 14:33 ` Jiri Kosina
2019-05-31 14:46 ` Andy Lutomirski
2019-05-31 14:54 ` Jiri Kosina
2019-05-31 15:26 ` Josh Poimboeuf
2019-05-31 15:41 ` Jiri Kosina
2019-05-31 16:19 ` Josh Poimboeuf
2019-05-31 16:51 ` Andy Lutomirski
2019-05-31 18:11 ` Josh Poimboeuf
2019-06-03 10:03 ` Rafael J. Wysocki
2019-05-31 16:23 ` Andy Lutomirski
2019-05-31 21:05 ` Jiri Kosina
2019-05-31 21:22 ` Andy Lutomirski
2019-06-03 14:23 ` Sean Christopherson
2019-06-03 15:24 ` Jiri Kosina
2019-06-03 16:18 ` Sean Christopherson
2019-05-31 12:09 ` Jiri Kosina
2019-05-31 14:51 ` Jiri Kosina
2019-05-31 12:18 ` Pavel Machek
2019-05-30 10:47 ` Pavel Machek
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=20190531051456.fzkvn62qlkf6wqra@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox