From: Peter Zijlstra <peterz@infradead.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Michele Ballabio <barra_cuda@katamail.com>,
linux-kernel@vger.kernel.org, fweisbec@gmail.com,
mingo@kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Bisected KVM hang on x86-32 between v3.12 and v3.13
Date: Mon, 7 Apr 2014 20:56:58 +0200 [thread overview]
Message-ID: <20140407185658.GK11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <5342EB78.3060002@gmx.de>
On Mon, Apr 07, 2014 at 08:16:24PM +0200, Toralf Förster wrote:
> v3.14-10353-g2b3a8fd works fine AFAICS
> (BTW the fix is stable material, right ?)
I'm fairly sure its not; its a rather invasive series; see:
2432e1364bbe x86: Nuke the supervisor_stack field in i386 thread_info
b807902a88c4 x86: Nuke GET_THREAD_INFO_WITH_ESP() macro for i386
0788aa6a23cb x86: Prepare removal of previous_esp from i386 thread_info structure
198d208df437 x86: Keep thread_info on thread stack in x86_32
Let me see if there's anything 'simpler' we can stuff in .13+
next prev parent reply other threads:[~2014-04-07 18:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 15:19 Bisected KVM hang on x86-32 between v3.12 and v3.13 Michele Ballabio
2014-04-06 15:52 ` Toralf Förster
2014-04-06 17:40 ` Michele Ballabio
2014-04-07 15:03 ` Peter Zijlstra
2014-04-07 15:07 ` Peter Zijlstra
2014-04-07 18:16 ` Toralf Förster
2014-04-07 18:56 ` Peter Zijlstra [this message]
2014-04-08 12:21 ` Peter Zijlstra
2014-04-08 19:14 ` Michele Ballabio
2014-04-08 19:51 ` Michele Ballabio
2014-04-08 20:28 ` Toralf Förster
2014-04-09 9:14 ` Stefan Bader
2014-04-09 9:45 ` Peter Zijlstra
2014-04-09 14:24 ` [PATCH -stable] x86,preempt: Fix preemption for i386 Peter Zijlstra
2014-04-09 14:36 ` Linus Torvalds
2014-04-09 19:19 ` Greg KH
2014-04-09 19:38 ` Peter Zijlstra
2014-04-09 19:57 ` Greg KH
2014-05-13 23:56 ` Greg KH
2014-04-07 18:59 ` Bisected KVM hang on x86-32 between v3.12 and v3.13 Frederic Weisbecker
2014-04-07 19:57 ` Toralf Förster
2014-04-07 22:43 ` Frederic Weisbecker
2014-04-07 19:49 ` Michele Ballabio
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=20140407185658.GK11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=barra_cuda@katamail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=toralf.foerster@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).