From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Spence Nick <Nick.Spence@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: RE: [PATCH] [POWERPC] Reintroduce O_SYNC flag to make DRAM non-cached.
Date: Thu, 08 May 2008 16:55:43 +1000 [thread overview]
Message-ID: <1210229743.1421.36.camel@pasglop> (raw)
In-Reply-To: <9E50B2A5FE44294CBF877745D9A4125F01D37125@az33exm24.fsl.freescale.net>
On Wed, 2008-05-07 at 23:31 -0700, Spence Nick wrote:
>
> In our case the memory area is reserved so that the main processor will
> not touch it except when mapped by the mem driver.
Then you should completely carve it out of the LMB's which will ensure
it's not seen as RAM by /dev/mem and not mapped by the linear mapping
(well, the later depends ... if it's carved out of the top of RAM it
should work fine, if it's a hole, I'm not sure we handle holes in the
linear mapping on 32 bits).
> Alternative solutions are to modify the user space code to flush out the
> caches by reading a large area, or to implement a board specific
> ppc_md.phys_mem_access_prot() function to do this.
>
> Either of these will meet my needs, but this will leave the O_SYNC flag
> ignored on the PowerPC architecture in 2.6, but honored by Linux 2.4 and
> other architectures. Probably not a problem for most people.
next prev parent reply other threads:[~2008-05-08 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 5:26 [PATCH] [POWERPC] Reintroduce O_SYNC flag to make DRAM non-cached nick.spence
2008-05-08 5:50 ` Paul Mackerras
2008-05-08 6:31 ` Spence Nick
2008-05-08 6:55 ` Benjamin Herrenschmidt [this message]
2008-05-08 7:17 ` Nick Spence
2008-05-08 7:21 ` Benjamin Herrenschmidt
2008-05-08 9:54 ` Segher Boessenkool
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=1210229743.1421.36.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Nick.Spence@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.