From: Alex Thorlton <athorlton@sgi.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Fabian Frederick <fabf@skynet.be>, Ingo Molnar <mingo@kernel.org>,
Russ Anderson <rja@sgi.com>
Subject: Re: [BUG] Possible locking issues in stop_machine code on 6k core machine
Date: Thu, 4 Dec 2014 09:58:53 -0600 [thread overview]
Message-ID: <20141204155853.GS4720@sgi.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1412032330510.16275@nanos>
On Thu, Dec 04, 2014 at 12:34:04AM +0100, Thomas Gleixner wrote:
> first of all, could you please format your mail so it is actually
> readable and can be replied to?
My fault there - stupid mistake.
> If you would provide real data instead of half baken assumptions
> we might actually be able to help you.
>
> There might be some hidden issue in the stomp machine crap, but surely
> not the one you described.
I'll return with some actual data so that others can get a better
picture of what we're seeing. I'll also see if I can come up with a
way to reproduce the issue on a smaller configuration; might not be
possible, but attempting to do so might provide some more insight into
our problem.
Thanks for your detailed description of the code path! I definitely
understand that our assumption can't be the actual problem here. I'll
dig back into the issue and try to get some better information.
Thanks again!
- Alex
prev parent reply other threads:[~2014-12-04 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 20:40 [BUG] Possible locking issues in stop_machine code on 6k core machine Alex Thorlton
2014-12-03 23:34 ` Thomas Gleixner
2014-12-04 15:58 ` Alex Thorlton [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=20141204155853.GS4720@sgi.com \
--to=athorlton@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rja@sgi.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.