From: Andrew Morton <akpm@osdl.org>
To: jes@trained-monkey.org (Jes Sorensen)
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch -mm series] ia64 specific /dev/mem handlers
Date: Tue, 22 Feb 2005 02:03:09 -0800 [thread overview]
Message-ID: <20050222020309.4289504c.akpm@osdl.org> (raw)
In-Reply-To: <16923.193.128608.607599@jaguar.mkp.net>
jes@trained-monkey.org (Jes Sorensen) wrote:
>
> Hi,
>
> This patch introduces ia64 specific read/write handlers for /dev/mem
> access which is needed to avoid uncached pages to be accessed through
> the cached kernel window which can lead to random corruption. It also
> introduces a new page-flag PG_uncached which will be used to mark the
> uncached pages. I assume this may be useful to other architectures as
> well where the CPU may use speculative reads which conflict with
> uncached access. In addition I moved do_write_mem to be under
> ARCH_HAS_DEV_MEM as it's only ever used if that is defined.
>
> The patch is needed for the new ia64 special memory driver (mspec -
> former fetchop).
>
> Patch is relative to 2.6.11-rc3-mm2 and relies on the ARCH_HAS_DEV_MEM
> flag which isn't in Linus' nor Tony's trees yet.
Is it possible to avoid consuming a page flag?
If this is an ia64-only (or 64-bit-only) thing I guess we could use bit 32.
> + if (page->flags & PG_uncached)
dude. That ain't gonna work ;)
next prev parent reply other threads:[~2005-02-22 10:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 9:52 [patch -mm series] ia64 specific /dev/mem handlers Jes Sorensen
2005-02-22 10:03 ` Andrew Morton [this message]
2005-02-22 12:08 ` Andi Kleen
2005-02-22 14:41 ` Jes Sorensen
2005-02-22 17:52 ` Matthew Wilcox
2005-02-22 19:25 ` Andrew Morton
2005-02-22 19:35 ` Dave Hansen
2005-02-22 21:38 ` Jes Sorensen
2005-02-23 0:48 ` Dave Hansen
2005-02-22 21:34 ` Jes Sorensen
2005-02-22 22:39 ` Jes Sorensen
2005-02-22 23:34 ` Andrew Morton
2005-02-23 10:01 ` Jes Sorensen
2005-02-23 22:34 ` Christoph Hellwig
2005-02-24 16:11 ` Jes Sorensen
2005-03-10 6:55 ` Andrew Morton
2005-03-10 13:49 ` Jes Sorensen
2005-02-22 22:03 ` Arjan van de Ven
2005-02-22 22:30 ` Jes Sorensen
2005-02-22 22:42 ` Arjan van de Ven
2005-02-23 8:12 ` Jes Sorensen
2005-02-23 8:24 ` Arjan van de Ven
2005-03-03 11:37 ` Andrew Morton
2005-03-03 12:53 ` Jes Sorensen
2005-03-04 12:26 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 18:05 Luck, Tony
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=20050222020309.4289504c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jes@trained-monkey.org \
--cc=linux-ia64@vger.kernel.org \
--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