From: "Phillip Lougher" <phillip.lougher@gmail.com>
To: "Siva Prasad" <sprasad@bivio.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: Variable "current" in Linux kernel...
Date: Mon, 16 Apr 2007 23:52:41 +0100 [thread overview]
Message-ID: <bffbecbb0704161552p7f62c800kd774809a41f177f0@mail.gmail.com> (raw)
In-Reply-To: <D83235F0F3C86D4D889D8B9A0DA8C6D75A76F1@corpexc01.corp.networkrobots.com>
On 4/16/07, Siva Prasad <sprasad@bivio.net> wrote:
>
> I would like to know where exactly the value of variable "current" gets
> changed.
current points to the task_struct structure of the currently running
process. It, obviously, changes each time the scheduler schedules
another process.
>
>
> BTW=85 did any one tried before to run from a different location of memor=
y
> than the usual 0x00000000? What are the main problems you faced? I know t=
his
> is open ended question, but wanted to see if any one ever did that.
>
I changed the 2.4 PPC kernel to do this about 5 years ago (for
Zarlink). Most of the issues relate to the PPC specific code, all
functions which map from a va->pa, from a pte->va, and vice-versa have
to be changed. The early start up assembly code has to be aware the
kernel is not running at zero, specifically the code which creates the
initial TLB entries. As far as I can recall, only one line of non-PPC
specific code needed to be changed. It is, however, a difficult task
which requires careful auditing of the code, and obviously knowledge
of the vm and memory allocator systems.
Phillip
next prev parent reply other threads:[~2007-04-16 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 21:56 Variable "current" in Linux kernel Siva Prasad
2007-04-16 22:52 ` Phillip Lougher [this message]
2007-04-17 15:12 ` Siva Prasad
2007-04-16 22:53 ` Andreas Schwab
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=bffbecbb0704161552p7f62c800kd774809a41f177f0@mail.gmail.com \
--to=phillip.lougher@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sprasad@bivio.net \
/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;
as well as URLs for NNTP newsgroup(s).