From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH][RFC] Add default CPU topology information
Date: Tue, 15 Apr 2008 12:42:31 -0700 [thread overview]
Message-ID: <20080415124231.e22df79e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080331114412.GH21637@solarflare.com>
On Mon, 31 Mar 2008 12:44:13 +0100
Ben Hutchings <bhutchings@solarflare.com> wrote:
> Not all architectures and configurations define CPU topology information.
> This can result in an empty topology directory in sysfs, and requires
> in-kernel users to protect all uses with #ifdef - see
> <http://marc.info/?l=linux-netdev&m=120639033904472&w=2>.
>
> The documentation of CPU topology specifies what the defaults should be
> if only partial information is available from the hardware. So we can
> provide these defaults as a fallback.
>
> This patch:
>
> - Adds default definitions of the 4 topology macros to
> include/asm-generic/topology.h.
> - Changes include/asm-*/topology.h to include <asm-generic/topology.h>
> unconditionally.
> - Changes drivers/base/topology.c to use the topology macros unconditionally
> and to cope with definitions that aren't lvalues.
> - Updates documentation accordingly.
>
I ran away in terror when I saw this patch. It's dark and dirty stuff
you're unearthing there and it looks like a minefield of compilation
problems. Not aided by the fact that we don't have a topology maintainer
afaik.
We shall see.
next prev parent reply other threads:[~2008-04-15 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 11:44 [PATCH][RFC] Add default CPU topology information Ben Hutchings
2008-03-31 12:35 ` Ingo Molnar
2008-04-15 19:42 ` Andrew Morton [this message]
2008-04-16 12:51 ` Ingo Molnar
2008-04-16 19:07 ` Andrew Morton
2008-04-18 6:45 ` Andrew Morton
2008-04-18 12:10 ` Ben Hutchings
2008-04-18 7:10 ` Andrew Morton
2008-04-18 7:32 ` Andrew Morton
2008-04-18 12:24 ` Ben Hutchings
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=20080415124231.e22df79e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhutchings@solarflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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