From: Brian Gerst <bgerst@didntduck.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@suse.de>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] percpu updates
Date: Mon, 06 May 2002 08:44:08 -0400 [thread overview]
Message-ID: <3CD67A98.40205@didntduck.org> (raw)
In-Reply-To: <3CD06ACE.1090402@didntduck.org> <3CD4B042.A4355FD3@zip.com.au> <3CD55FF0.2030909@didntduck.org> <3CD64562.9AB4D3D7@zip.com.au>
Andrew Morton wrote:
> Brian Gerst wrote:
>
>>Andrew Morton wrote:
>>
>>>Brian Gerst wrote:
>>>
>>>
>>>>These patches convert some of the existing arrays based on NR_CPUS to
>>>>use the new per cpu code.
>>>>
>>>
>>...
>>Andrew, could you try this patch? I suspect something in setup_arch()
>>is touching the per cpu area before it gets copied for the other cpus.
>>This patch makes certain the boot cpu area is setup ASAP.
>
>
> This little recidivist is still using gcc-2.91.66. It is not
> placing the percpu data in the correct section. It is not
> entirely obvious why.
>
> I downgraded to 2.95.3 (build time went from 2:45 to 3:15, giving
> nothing in return) and Brian's patch worked OK.
>
> ho hum. So. 2.91.66, rest in peace. I shall miss you.
Aha. I was starting to wonder about the compiler.
--
Brian Gerst
next prev parent reply other threads:[~2002-05-06 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 22:23 [PATCH] percpu updates Brian Gerst
2002-05-01 22:44 ` Andrew Morton
2002-05-01 22:54 ` Brian Gerst
2002-05-01 23:05 ` Randy.Dunlap
2002-05-01 23:35 ` Alan Cox
2002-05-03 14:59 ` Timothy D. Witham
2002-05-05 4:08 ` Andrew Morton
2002-05-05 16:38 ` Brian Gerst
2002-05-06 8:57 ` Andrew Morton
2002-05-06 12:44 ` Brian Gerst [this message]
2002-05-06 7:27 ` Rusty Russell
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=3CD67A98.40205@didntduck.org \
--to=bgerst@didntduck.org \
--cc=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/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.