From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [rfc] generic allocator and mspec driver
Date: Tue, 15 Feb 2005 17:35:46 +0000 [thread overview]
Message-ID: <20050215173546.GB15050@esmail.cup.hp.com> (raw)
In-Reply-To: <16897.9640.160896.31584@jaguar.mkp.net>
On Tue, Feb 15, 2005 at 03:43:10AM -0500, Jes Sorensen wrote:
> None of the ones I know well have this problem, but I have little
> knowledge about this level of stuff on most architectures. The ones
> that could have issues would probably be like PPC, PARISC and maybe
> Alpha .....
With parisc 2.0 CPU, one could map the same physical address
as both cacheable and uncacheable via two entries in the page table.
AFAIK, the uncacheable bit is only use to map MMIO address space.
In practice, I'm not sure what happens since I'm not aware of
any need for both mappings at the same time because we can use
"LDWA" (Load Word Absolute). LDWA can load from (almost) any physical
address and is by nature uncached (caches are VIVT).
Older PA1.x CPU had hardwired 0xf0000000-0xffffffff to be uncacheable.
I.e. it's not possible to have an overlap.
hth,
grant
next prev parent reply other threads:[~2005-02-15 17:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 19:10 [rfc] generic allocator and mspec driver Jes Sorensen
2005-02-02 19:46 ` Jesse Barnes
2005-02-02 23:33 ` Jack Steiner
2005-02-03 7:47 ` Jes Sorensen
2005-02-03 8:38 ` Jes Sorensen
2005-02-03 11:19 ` Robin Holt
2005-02-03 14:55 ` Jes Sorensen
2005-02-03 17:06 ` Jesse Barnes
2005-02-03 17:31 ` Dean Roe
2005-02-03 17:31 ` Robin Holt
2005-02-03 17:41 ` Jesse Barnes
2005-02-03 18:54 ` Jack Steiner
2005-02-03 19:39 ` David Mosberger
2005-02-03 20:58 ` Jes Sorensen
2005-02-03 21:40 ` Luck, Tony
2005-02-04 1:00 ` David Mosberger
2005-02-13 21:57 ` Jes Sorensen
2005-02-14 19:12 ` Luck, Tony
2005-02-14 19:17 ` David Mosberger
2005-02-15 8:43 ` Jes Sorensen
2005-02-15 8:44 ` Jes Sorensen
2005-02-15 17:35 ` Grant Grundler [this message]
2005-02-15 18:04 ` David Mosberger
2005-02-15 18:05 ` David Mosberger
2005-02-15 19:11 ` Robin Holt
2005-02-15 19:19 ` David Mosberger
2005-02-15 19:49 ` Robin Holt
2005-02-15 19:59 ` Jes Sorensen
2005-02-15 20:02 ` Jes Sorensen
2005-02-15 20:24 ` Robin Holt
2005-02-16 7:32 ` Jes Sorensen
2005-02-16 14:17 ` Jes Sorensen
2005-02-16 17:50 ` Luck, Tony
2005-02-16 18:18 ` Luck, Tony
2005-02-16 19:10 ` Jes Sorensen
2005-02-16 21:02 ` David Mosberger
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=20050215173546.GB15050@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=linux-ia64@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