From: Arjan van de Ven <arjanv@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, davej@redhat.com
Subject: Re: 2.6.1-rc1 arch/i386/kernel/setup.c wrong parameter order to request resources ?
Date: Sun, 4 Jan 2004 23:00:05 +0100 [thread overview]
Message-ID: <20040104220005.GA10814@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401041305440.2162@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Sun, Jan 04, 2004 at 01:08:52PM -0800, Linus Torvalds wrote:
>
>
> On Sun, 4 Jan 2004, Arjan van de Ven wrote:
> >
> > in setup.c the kernel tries to reserve ram resources for system ram etc
> > etc. However it seems it's done with the parameters to request_resource in
> > the wrong order (it certainly is opposite order from other neighboring
> > code). Can someone confirm I'm not overlooking something?
>
> You've overlooked something.
>
> The core uses the rigth order: it's literally trying to find _which_ of
> the e820 resources contains the "code" and "data" resource.
>
> In other words: the code and data resources don't contain anything. They
> are contained _in_ something, but we don't know which one off-hand, so we
> try to register them in all the memory resources we find.
> and not used for anything else.
ok fair enough; maybe deserves more comment but it makes sense.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-04 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 15:39 2.6.1-rc1 arch/i386/kernel/setup.c wrong parameter order to request resources ? Arjan van de Ven
[not found] ` <Pine.LNX.4.58.0401041305440.2162@home.osdl.org>
2004-01-04 22:00 ` Arjan van de Ven [this message]
2004-03-29 15:43 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 15:42 Arjan van de Ven
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=20040104220005.GA10814@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.