public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Len Brown <lenb@kernel.org>, Ingo Molnar <mingo@elte.hu>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20-git: undefined reference to `smp_call_function_single'
Date: Sat, 17 Feb 2007 19:42:38 +0100	[thread overview]
Message-ID: <1171737758.30834.154.camel@localhost.localdomain> (raw)
In-Reply-To: <1171736745.3379.24.camel@mulgrave.il.steeleye.com>

On Sat, 2007-02-17 at 12:25 -0600, James Bottomley wrote:
> > Yup, this obscure machine is missing smp_call_function_single().
> > 
> > James ?
> 
> Where's this coming from?  smp_call_function_single() is an obscure kvm
> only API think for x86/ia64 ... it's not supported on any other
> architecure.  The symbol you have is blowing up in the kernel
> subdirectory which suggests someone has tried to use it in generic code,
> which will fail to compile on a lot more than voyager and parisc ...

smp_call_function_single() was added with commit:
eaa70773e750cc09d60938bceacd028bc76b8e3a

   [PATCH] i386: add smp_call_function_single
    
    Continiung the series of small patches necessary for the perfmon subsystem,
    here is a patch that adds support for the smp_call_function_single()
    function for i386.  It exists for almost all other architectures but i386.
    The perfmon subsystem needs it in one case to free some state on a
    designated remote CPU.

It's not an obscure kvm API :) But the claim that it is available on
almost all other architectures but i386 is wrong. Only x86_64, ia64 and
i386 have it.

The function is defined in include/linux/smp.h and there is no
indication that it is an architecture specific thingy. What a steaming
pile of ....

/me grumbles

	tglx



  reply	other threads:[~2007-02-17 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17  2:08 2.6.20-git: undefined reference to `smp_call_function_single' Len Brown
2007-02-17 10:25 ` Thomas Gleixner
2007-02-17 18:25   ` James Bottomley
2007-02-17 18:42     ` Thomas Gleixner [this message]
2007-02-17 19:03       ` [PATCH] tick management: make broadcast dependent on local APIC Thomas Gleixner
2007-03-10  3:09         ` Len Brown

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=1171737758.30834.154.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=lenb@kernel.org \
    --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