From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: exporting __cpu_physical_id
Date: Mon, 21 May 2001 18:38:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005634@msgid-missing> (raw)
I assume you're using cpu_physical_id() in your code? I don't mind
exporting the physical id array, but Asit sent me an SMP cleanup patch
which renames __cpu_physical_id to ia64_cpu_to_sapicid, so the actual
name exported will be different. As long as your code uses
cpu_physical_id(), you'll be fine, though.
--david
>>>>> On Mon, 21 May 2001 17:33:17 +0200 (MEST), Erich Focht <focht@ess.nec.de> said:
Erich> Hello, does anything speak against adding the line
Erich> EXPORT_SYMBOL(__cpu_physical_id);
Erich> somewhere into arch/ia64/kernel/smp.c ? I'd need to use the
Erich> hardware CPU IDs from within a loadable module and I didn't
Erich> find any other 'exported' function or array with the needed
Erich> information...
Erich> Thanks in advance!
Erich> Best regards, Erich
next reply other threads:[~2001-05-21 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 18:38 David Mosberger [this message]
2001-05-21 22:22 ` [Linux-ia64] Re: exporting __cpu_physical_id Erich Focht
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=marc-linux-ia64-105590693005634@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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