From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@rostedt.homelinux.com>,
723180@bugs.debian.org, Brian Silverman <bsilver16384@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT"
Date: Mon, 6 Jan 2014 12:32:30 +0100 [thread overview]
Message-ID: <20140106113230.GA25261@linutronix.de> (raw)
In-Reply-To: <20140104181807.GS20765@two.firstfloor.org>
* Andi Kleen | 2014-01-04 19:18:07 [+0100]:
>On Fri, Jan 03, 2014 at 02:55:48PM +0100, Sebastian Andrzej Siewior wrote:
>> where do I start. Let me explain what is going on here. The code
>> sequence
>
>Yes the IST stacks are needed for correctness, even in more cases than
>the example below. You cannot just disable them, just because you don't
>like them.
Andi, you were the Author of that patch.
I plan to migrate from the IST stack to the kernel stack so I can enable
preemption. This is he case on 32bit. You mention more cases than this.
Could you please give me some examples so I can consider them?
>-Andi
Sebastian
prev parent reply other threads:[~2014-01-06 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130917061329.4872.51468.reportbug@dell-inspiron-linux.dlinkrouter>
[not found] ` <1379427451.23881.48.camel@deadeye.wl.decadent.org.uk>
[not found] ` <CAP01z6LVxoA6kDJeL8NuO2aA22BjMvXSk9ZY7z9cOK1=k56vpg@mail.gmail.com>
[not found] ` <1379905562.3913.8.camel@deadeye.wl.decadent.org.uk>
[not found] ` <CAP01z6+j6moUio9pc3G3iz+ebJCdKEvngddxnxazRP+NXwLkyg@mail.gmail.com>
2013-09-25 13:24 ` Double fault when single-stepping compat task with PREEMPT_RT Ben Hutchings
2013-12-15 19:33 ` Sebastian Andrzej Siewior
2014-01-03 13:55 ` [PATCH] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT" Sebastian Andrzej Siewior
2014-01-04 18:18 ` Andi Kleen
2014-01-05 4:45 ` Mike Galbraith
2014-01-05 5:05 ` Mike Galbraith
2014-01-05 18:04 ` Andi Kleen
2014-01-06 11:32 ` Sebastian Andrzej Siewior [this message]
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=20140106113230.GA25261@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=723180@bugs.debian.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=ben@decadent.org.uk \
--cc=bsilver16384@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@rostedt.homelinux.com \
--cc=tglx@linutronix.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 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.