From: Steffen Persvold <sp@scali.no>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Status on ioremap patch
Date: Sun, 06 Jan 2002 11:02:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805752@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805186@msgid-missing>
Keith Owens wrote:
>
> On Sat, 05 Jan 2002 16:01:29 +0100,
> Steffen Persvold <sp@scali.no> wrote:
> >--- linux-2.4.17/mm/memory.c.orig Fri Dec 21 18:42:05 2001
> >+++ linux-2.4.17/mm/memory.c Sat Jan 5 13:13:26 2002
> >@@ -791,6 +791,9 @@
> > * maps a range of physical memory into the requested pages. the old
> > * mappings are removed. any references to nonexistent pages results
> > * in null mappings (currently treated as "copy-on-access")
> >+ *
> >+ * For physical (or I/O) memory mapped into the kernel virtual space,
> >+ * the old mappings will not be removed.
>
> That comment worries me. If you have multiple mappings for the same
> page then you may have problems on hardware that uses virtually indexed
> caches. Two virtual addresses could map to the same physical page but
> index to different cache lines, destroying cache coherency. How do you
> prevent that?
>
Well, actually multiple mappings in kernel space is denied :
+ if (address > VMALLOC_START && address < VMALLOC_END) {
+ if (!pte_none(*pte)) {
+ printk("remap_area_pte: page already exists\n");
+ BUG();
+ }
+ set_pte(pte, mk_pte_phys(phys_addr, prot));
+ } else {
+ struct page *page;
+ pte_t oldpage;
+ oldpage = ptep_get_and_clear(pte);
+
+ page = virt_to_page(__va(phys_addr));
+ if ((!VALID_PAGE(page)) || PageReserved(page))
+ set_pte(pte, mk_pte_phys(phys_addr, prot));
+ forget_pte(oldpage);
+ }
Regards,
--
Steffen Persvold | Scalable Linux Systems | Try out the world's best
mailto:sp@scali.no | http://www.scali.com | performing MPI implementation:
Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 -
Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
next prev parent reply other threads:[~2002-01-06 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 23:14 [Linux-ia64] Re: Status on ioremap patch David Mosberger
2001-09-15 12:36 ` Steffen Persvold
2001-09-28 12:39 ` Jes Sorensen
2002-01-05 15:01 ` Steffen Persvold
2002-01-05 23:30 ` Keith Owens
2002-01-06 11:02 ` Steffen Persvold [this message]
2002-01-06 11:55 ` Keith Owens
2002-01-06 14:27 ` Steffen Persvold
2002-01-09 20:01 ` Steffen Persvold
2002-01-10 3:01 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2004-03-03 15:12 Hugo Kohmann
2004-03-03 22:58 ` 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=marc-linux-ia64-105590698805752@msgid-missing \
--to=sp@scali.no \
--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