From: Pantelis Antoniou <panto@intracom•gr>
To: joakim.tjernlund@lumentis•se
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: kmalloc and startup process
Date: Tue, 17 Dec 2002 15:40:38 +0200 [thread overview]
Message-ID: <3DFF2956.6020903@intracom.gr> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLKEODFIAA.joakim.tjernlund@lumentis.se>
Joakim Tjernlund wrote:
>Don't know when it's safe to call kmalloc, but maybe you
>should avoid kmalloc? Is it possible to use
>kmalloc when the microcode(8xx_io/micropatch.c) is loaded?
>
> Jocke
>
I fixed the problem via another way.
At startup I use a statically allocated area, or
the bootmem allocated page.
The kmalloc is used only when a request for memory
cannot be satisfied by this memory.
I will probably post the patch for the hostmem today,
followed tommorow by the patch for the dpmem.
Stay tuned.
>>
>>Hi
>>
>>I'm hacking now the 8xx hostalloc and dpalloc stuff,
>>and I have a a question.
>>
>>At what point in the startup process is it OK to call
>>kmalloc?
>>
>>I don't think it is safe at the setup_arch point.
>>
>>Is this correct?
>>
>>Thanks
>>
>>--
>>Pantelis Antoniou
>>INTRACOM S.A. Greece
>>
>>
>>
>>
>>
>
>
--
Pantelis Antoniou
INTRACOM S.A. Greece
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-17 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 12:52 kmalloc and startup process Pantelis Antoniou
2002-12-17 13:19 ` Joakim Tjernlund
2002-12-17 13:40 ` Pantelis Antoniou [this message]
2002-12-17 15:06 ` Pantelis Antoniou
2002-12-17 16:44 ` Dan Malek
2002-12-18 12:34 ` Pantelis Antoniou
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=3DFF2956.6020903@intracom.gr \
--to=panto@intracom$(echo .)gr \
--cc=joakim.tjernlund@lumentis$(echo .)se \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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