From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Colin Cross <ccross@android.com>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@redhat.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Mandeep Singh Baines <msb@chromium.org>,
Paul Walmsley <paul@pwsan.com>, Al Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Ben Chan <benchan@chromium.org>
Subject: Re: [PATCH 2/2] lockdep: check that no locks held at freeze time
Date: Mon, 6 May 2013 16:42:48 +0200 [thread overview]
Message-ID: <20130506144248.GB15446@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFzVNwCJhvp4f0EcHK3Vk1ZVKY0fAeu-6FdjhCFiafTAPQ@mail.gmail.com>
On Mon, May 06, 2013 at 07:33:28AM -0700, Linus Torvalds wrote:
> On Mon, May 6, 2013 at 1:55 AM, Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > Doesn't i386 have all the funny per-cpu stuff too? So the only reason it still
> > does the fugly stack based thing is because nobody could be arsed to do the
> > work of converting it.
>
> Umm. That "fugly stack-based" thing is better than the per-cpu crap.
>
> The percpu stuff implies a memory load. The stack based thing gets
> thread_info with pure register accesses. Much better.
>
> For "current()" the per-cpu thing may be better, but if you actually
> need the thread-info (not the case here, but in other places), the
> stack masking is superior when it works (ie when you don't have
> multi-stack issues due to irq's etc)
But you can do both right? Use per-cpu for current and stack frobbery for
current_thread_info().
That said, ISTR some risky bits where the stack frobbery went awry due to
irq-stacks which is the source for my feelings towards the stack frobbery.
That and of course that i386 and x86-64 behave differently for no apparent
reason.
next prev parent reply other threads:[~2013-05-06 14:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 21:04 [PATCH 1/2] freezer: add unsafe versions of freezable helpers Colin Cross
2013-05-03 21:04 ` [PATCH 2/2] lockdep: check that no locks held at freeze time Colin Cross
2013-05-04 13:04 ` Pavel Machek
2013-05-04 20:27 ` Colin Cross
2013-05-04 22:57 ` Pavel Machek
2013-05-04 23:49 ` Colin Cross
2013-05-05 0:05 ` Pavel Machek
2013-05-05 0:23 ` Colin Cross
2013-05-05 1:13 ` Pavel Machek
2013-05-05 9:18 ` Ingo Molnar
2013-05-06 8:55 ` Peter Zijlstra
2013-05-06 12:11 ` Pavel Machek
2013-05-06 14:33 ` Linus Torvalds
2013-05-06 14:42 ` Peter Zijlstra [this message]
2013-05-06 19:01 ` Tejun Heo
2013-05-06 19:30 ` Colin Cross
2013-05-06 19:33 ` Tejun Heo
2013-05-06 20:06 ` Rafael J. Wysocki
2013-05-04 13:00 ` [PATCH 1/2] freezer: add unsafe versions of freezable helpers Pavel Machek
2013-05-04 20:23 ` Colin Cross
2013-05-04 22:55 ` Pavel Machek
2013-05-05 9:23 ` Ingo Molnar
2013-05-05 22:12 ` Pavel Machek
2013-05-06 8:50 ` Peter Zijlstra
2013-05-06 10:58 ` Jeff Layton
2013-05-06 10:56 ` Jeff Layton
2013-05-06 19:57 ` Colin Cross
2013-05-06 21:43 ` Jeff Layton
2013-05-06 21:54 ` Colin Cross
2013-05-06 21:58 ` Linus Torvalds
2013-05-06 22:05 ` Jeff Layton
2013-05-06 22:11 ` Colin Cross
2013-05-06 22:14 ` Tejun Heo
2013-05-06 21:59 ` Jeff Layton
2013-05-06 18:55 ` Tejun Heo
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=20130506144248.GB15446@dyad.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=akpm@osdl.org \
--cc=benchan@chromium.org \
--cc=bfields@fieldses.org \
--cc=ccross@android.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=msb@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=paul@pwsan.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®