public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Brian Gerst <brgerst@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Tejun Heo <htejun@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage
Date: Tue, 27 Jan 2009 16:53:21 +0000	[thread overview]
Message-ID: <1233075201.3231.59.camel@localhost.localdomain> (raw)
In-Reply-To: <73c1f2160901270825y5e7f3974m830c399074c2e8f1@mail.gmail.com>

On Tue, 2009-01-27 at 11:25 -0500, Brian Gerst wrote:
> To be fair, setup_percpu.c isn't built on UP.  But we're splitting
> hairs over just 3 conditional variables.  I'm open to ideas, but I'm
> quite certain that any general solution will have more overhead than
> the current code.  I am looking at a patch to remove the early percpu
> pointers, so the second set of ifdefs would go away.

Well, how much do you need rid of?  All the local apic stuff can move
into apic.c as something like x86_percpu_apic_setup(cpu) for the in loop
stuff and x86_percpu_apic_global() for the rest ... these then become
weak empty functions in setup_percpu.c.  That elimiates the alleged
voyager problem.

The other cases are nastier:  there's a numa case, an x86_84 case and a
both numa and x86_64 case.  We only have files for the x86_64 case.  At
a stretch the numa cases could move into mm/numa_${BITS}.c

This isn't really hugely critical path so this type of approach would
work ... I can cook up a patch if it's acceptable? 

James



  reply	other threads:[~2009-01-27 16:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090126103243.GA31307@elte.hu>
2009-01-26 13:44 ` [PATCH] x86-32: Fix __per_cpu_load relocation Brian Gerst
2009-01-26 14:18   ` Ingo Molnar
2009-01-27  2:02     ` Tejun Heo
2009-01-27  4:03       ` Tejun Heo
2009-01-27  5:03         ` James Bottomley
2009-01-27  5:29           ` [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage Tejun Heo
2009-01-27  5:29             ` [PATCH 2/2 #tj-percpu] x86: clean up indentation in setup_per_cpu_areas() Tejun Heo
2009-01-27 11:37             ` [PATCH 1/2 #tj-percpu] x86: fix build breakage on voyage Ingo Molnar
2009-01-27 11:47               ` Tejun Heo
2009-01-27 12:50                 ` Brian Gerst
2009-01-27 13:11                 ` Ingo Molnar
2009-01-27 13:21                   ` Ingo Molnar
2009-01-27 15:33                 ` James Bottomley
2009-01-27 15:31               ` James Bottomley
2009-01-27 15:50                 ` Ingo Molnar
2009-01-27 16:04                   ` James Bottomley
2009-01-27 16:25                     ` Brian Gerst
2009-01-27 16:53                       ` James Bottomley [this message]
2009-01-27 10:52         ` [PATCH] x86-32: Fix __per_cpu_load relocation Ingo Molnar

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=1233075201.3231.59.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=brgerst@gmail.com \
    --cc=htejun@gmail.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