From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] mmaping with VIVT cache
Date: Mon, 20 Sep 2010 11:50:19 +0100 [thread overview]
Message-ID: <20100920105019.GB30793@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <a4e3b92bbd5f9f04fa06dd5d3f2f160a@cox.rootnode.net>
On Mon, Sep 20, 2010 at 11:38:44AM +0100, Pawel Moll wrote:
> > However, in this case, architectures using VIPT aliasing caches will
> > also trip over it - has anyone used this webcam on something like
> > Sparc or powerpc? I'm guessing that it'll fail there too...
>
> It wasn't a webcam but USB audio card, not sparc nor powerpc but sh but
> the I believe problem stays the same - vmalloc-ed buffer mapped into the
> user-space...
>
> http://thread.gmane.org/gmane.linux.alsa.devel/55882/focus=7160
>
> I've ended up with pgprot_noncached(), as there was no "alias-safe API"
> available, and apparently it's still the case? ;-)
pgprot_noncached will be unsafe on ARMv6 and ARMv7 architectures when
used for mapping existing memory, as you'll be violating an architectural
restriction (having aliasing mappings of memory as 'Strongly ordered'
when there is a pre-existing 'Memory' type mapping.)
next prev parent reply other threads:[~2010-09-20 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 19:07 [RFC] mmaping with VIVT cache P F
2010-09-17 21:06 ` Russell King - ARM Linux
2010-09-20 10:38 ` Pawel Moll
2010-09-20 10:50 ` Russell King - ARM Linux [this message]
2010-09-20 11:31 ` Pawel Moll
-- strict thread matches above, loose matches on Subject: below --
2010-09-16 0:25 P F
2010-09-16 23:05 ` Russell King - ARM Linux
2010-09-13 19:58 P F
2010-09-14 23:50 ` Russell King - ARM Linux
2010-09-15 1:06 ` Eric Miao
2010-09-15 7:31 ` Russell King - ARM Linux
2010-09-15 7:37 ` Eric Miao
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=20100920105019.GB30793@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).