From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: Franck Bui-Huu <vagabon.xyz@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] setup.c: introduce __pa_symbol() and get ride of CPHYSADDR()
Date: Mon, 09 Oct 2006 16:25:46 +0200 [thread overview]
Message-ID: <452A5BEA.2060500@innova-card.com> (raw)
In-Reply-To: <20061009132131.GA18308@networkno.de>
Thiemo Seufer wrote:
> Franck Bui-Huu wrote:
>> Thiemo Seufer wrote:
>>> Franck Bui-Huu wrote:
>>>> - if (CPHYSADDR(initrd_end) > PFN_PHYS(max_low_pfn)) {
>>>> + if (__pa(initrd_end) > PFN_PHYS(max_low_pfn)) {
>>> ISTR this failed on O2, where kernel+initrd are loaded into KSEG0 but the
>>> PAGE_OFFSET is for XKPHYS.
>>>
>> I guess that you were meaning somthing like:
>>
>> LOADADDR = 0xffffffff80004000
>> PAGE_OFFSET = 0xa800000000000000
>>
>> is that correct ?
>
> Yes.
>
>> If so could you explain the choice of these values
>> because I fail to understand it.
>
> It allows to load a 64-bit kernel in KSEG0,
sorry to be ignorant of 64 bit kernels, but what's the point
to load them in KSEG0.
> and use short 2-instruction symbol references there.
do you mean "it allows to use only 2 'lui' instructions to load
a symbol address into a register" ?
Futhermore I don't see how some part of the kernel convert virtual
address into a physical one with such values. For example in setup.c,
the function resource_init() does:
code_resource.start = virt_to_phys(&_text);
code_resource.end = virt_to_phys(&_etext) - 1;
data_resource.start = virt_to_phys(&_etext);
data_resource.end = virt_to_phys(&_edata) - 1;
How does it work in this case ?
Thanks
Franck
next prev parent reply other threads:[~2006-10-09 14:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 13:36 [PATCH] setup.c: introduce __pa_symbol() and get ride of CPHYSADDR() Franck Bui-Huu
2006-10-06 17:21 ` Thiemo Seufer
2006-10-09 11:58 ` Franck Bui-Huu
2006-10-09 13:21 ` Thiemo Seufer
2006-10-09 14:25 ` Franck Bui-Huu [this message]
2006-10-09 14:58 ` Thiemo Seufer
2006-10-09 15:30 ` Franck Bui-Huu
2006-10-09 15:51 ` Atsushi Nemoto
2006-10-09 16:59 ` Thiemo Seufer
2006-10-10 8:49 ` Atsushi Nemoto
2006-10-10 13:49 ` Franck Bui-Huu
2006-10-10 14:19 ` Atsushi Nemoto
2006-10-10 15:01 ` Franck Bui-Huu
2006-10-10 15:29 ` Atsushi Nemoto
2006-10-10 16:04 ` Franck Bui-Huu
2006-10-10 16:16 ` Franck Bui-Huu
2006-10-10 21:51 ` Ralf Baechle
2006-10-11 3:11 ` Atsushi Nemoto
2006-10-11 9:37 ` Franck Bui-Huu
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=452A5BEA.2060500@innova-card.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=ths@networkno.de \
/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