[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1905310139380.1962@cbobk.fhfr.pm>
Date: Fri, 31 May 2019 01:42:02 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
the arch/x86 maintainers <x86@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] x86/power: Fix 'nosmt' vs. hibernation triple fault
during resume
On Thu, 30 May 2019, Josh Poimboeuf wrote:
> > > Reviewed-by: Thomas Gleixner <tglx@...utronix.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.
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists