All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu
Date: Thu, 17 Oct 2002 01:08:18 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805176@msgid-missing> (raw)

On 2.5.39, 
it fails to insmod some modules that refers to "cpu_info__per_cpu".
That global IS DEFINE_PER_CPU'd, DECLARE_PER_CPU'd and is in System.map but
for some reason it fails to resolve.
Have you guys seen this ?

thanks
J.I.

-----Original Message-----
From: Luck, Tony [mailto:tony.luck@intel.com]
Sent: Wednesday, October 16, 2002 10:56 AM
To: Luck, Tony; linux ia64 kernel list
Cc: linux-kernel@vger.kernel.org
Subject: RE: [Linux-ia64] [patch 2.5.39] allow kernel to be virtually
mapp ed from any physi cal address


Yesterday I wrote:
> This patch provides just the code needed to virtually map the
> kernel to a fixed virtual address from whatever physical address
> it happened to be loaded at (it is assumed that the bootloader
> handled the issue of finding a suitably aligned piece of memory).

Elilo already knows how to find memory, as long as you either use
the "relocatable" keyword in elilo.conf, or the "-r" command-line
option to let it know that it is OK to relocate.

Using this elilo option means that the changes I provided for
vmlinux.ld.S can be very slightly simplified, it isn't necessary
to define BASE_KVADDR as "KERNEL_START + KERNEL_TR_PAGE_SIZE", you
can just use:

#define BASE_KVADDR	KERNEL_START

-Tony

_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


             reply	other threads:[~2002-10-17  1:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17  1:08 Lee, Jung-Ik [this message]
2002-10-17  7:45 ` [Linux-ia64] Some Modules fail w/ unresolved cpu_info__per_cpu Christian Cotte-Barrot
2002-10-17  8:19 ` Keith Owens
2002-10-17 10:31 ` Christian Cotte-Barrot
2003-02-19 11:55 ` Christian Cotte-Barrot

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-105590709805176@msgid-missing \
    --to=jung-ik.lee@intel.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 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.