From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: for_each_online_cpu broken ?
Date: Thu, 8 Dec 2005 01:43:12 -0500 [thread overview]
Message-ID: <20051208064312.GG28201@redhat.com> (raw)
In-Reply-To: <20051208063050.GL11190@wotan.suse.de>
On Thu, Dec 08, 2005 at 07:30:50AM +0100, Andi Kleen wrote:
> > This was seen with a .15rc5-git1 kernel.
> > Is this something still living in your x86-64 patchset or -mm ?
>
> Only the change for less additional CPUs.
Ok, then I'm at a loss why it's dumping state for NR_CPUS cpus.
I'm away tomorrow, but I'll poke at it some more on Friday.
Dave
prev parent reply other threads:[~2005-12-08 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 5:07 for_each_online_cpu broken ? Dave Jones
2005-12-08 5:26 ` Andi Kleen
2005-12-08 5:33 ` Dave Jones
2005-12-08 5:38 ` David S. Miller
2005-12-08 6:12 ` Andi Kleen
2005-12-08 6:27 ` Dave Jones
2005-12-08 6:22 ` Nigel Cunningham
2005-12-08 6:28 ` Dave Jones
2005-12-08 6:30 ` Andi Kleen
2005-12-09 0:03 ` Nigel Cunningham
2005-12-08 6:30 ` Andi Kleen
2005-12-08 6:43 ` Dave Jones [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=20051208064312.GG28201@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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