From: gshan <gshan@alcatel-lucent.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Chen, Jinmin (Jinmin)" <jinminc@alcatel-lucent.com>
Subject: Questions on one PowerPC assembly instruction from hash_page
Date: Mon, 18 Jun 2007 16:33:22 +0800 [thread overview]
Message-ID: <46764352.4000805@alcatel-lucent.com> (raw)
In-Reply-To: <20070618070519.GR6149@kernel.dk>
Hey Guys,
I can't understand the following instructions from
arch/ppc/mm/hashtable.S::hash_page. If I got the right design, the
following instruction is to get the PMD (Page Middle Descritor) because
Linux for 32-bits PowerPC cut page table into 3 domains: root, PMD, PTE.
The top bits (22 to 31 bit) is the index for PMD, and the next 10 bits
(12 to 21 bit) is the index for PTE in the associative PMD. The
remaining 12 bits (0 to 11 bit) indicated the page size (4KB). However,
the following instruction polled [8-17] bits instead of [22-31] bits as
expected. Anybody could give me answer?
r4 is the address that caused the DSI
r5 is the address of swapper_pg_dir if we are under kernel mode.
rlwimi r5,r4,12,20,29 /* insert top 10 bits of address */
Thanks,
Gavin
next prev parent reply other threads:[~2007-06-18 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 14:24 [PATCH] cdrom_sysctl_info fix Dave Young
2007-06-14 6:40 ` dave young
2007-06-14 15:43 ` Randy Dunlap
2007-06-15 0:11 ` dave young
2007-06-15 1:41 ` Randy Dunlap
2007-06-15 5:58 ` Jens Axboe
2007-06-15 14:33 ` Dave Young
2007-06-15 13:26 ` Jens Axboe
2007-06-18 12:58 ` Dave Young
2007-06-18 6:27 ` Jens Axboe
2007-06-18 6:41 ` dave young
2007-06-18 6:43 ` Jens Axboe
2007-06-18 7:03 ` dave young
2007-06-18 7:05 ` Jens Axboe
2007-06-18 8:33 ` gshan [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 8:57 Questions on one PowerPC assembly instruction from hash_page Mikael Pettersson
2007-06-19 2:18 ` gshan
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=46764352.4000805@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=jinminc@alcatel-lucent.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox