From: Russell King <rmk+alsa@arm.linux.org.uk>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "Gupta, Kshitij" <kshitij@ti.com>, alsa-devel@lists.sourceforge.net
Subject: Re: buffer producer/consumer sync
Date: Tue, 9 Mar 2004 10:43:46 +0000 [thread overview]
Message-ID: <20040309104346.C1987@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0403091122140.3966@pnote.perex-int.cz>; from perex@suse.cz on Tue, Mar 09, 2004 at 11:23:45AM +0100
On Tue, Mar 09, 2004 at 11:23:45AM +0100, Jaroslav Kysela wrote:
> Ok, I though that vma->vm_page_prot fix is sufficient for this purpose but
> appearently not.
Unfortunately not - as the code currently stands, not only are
userspace mappings cached, but also kernel mappings of the same pages.
Unfortunately changing userspace mappings to be uncached only solves
half the problem. We also need to solve the kernel space problem as
well. However, this needs to be done in an architecture specific way,
which in turn means sorting out something which architecture people
are happy with.
Then there's the issue about the abuse of virt_to_page() taking a
mapped virtual address (ie from pci_alloc_consistent or
dma_alloc_coherent) rather than a direct-mapped virtual address
(alloc_pages / kmalloc).
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-09 10:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 9:51 buffer producer/consumer sync Gupta, Kshitij
2004-03-09 9:53 ` Jaroslav Kysela
2004-03-09 10:18 ` Russell King
2004-03-09 10:23 ` Jaroslav Kysela
2004-03-09 10:43 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 10:40 Gupta, Kshitij
2004-03-09 11:33 Gupta, Kshitij
2004-03-09 11:46 ` Russell King
2004-03-31 5:02 Gupta, Kshitij
2004-03-31 7:31 ` Russell King
2004-03-31 7:44 ` Jaroslav Kysela
2004-03-31 7:53 ` Russell King
2004-03-31 8:10 ` Jaroslav Kysela
2004-03-31 8:11 ` Russell King
2004-03-31 8:29 ` Jaroslav Kysela
2004-03-31 8:53 ` Russell King
2004-03-31 9:07 ` Jaroslav Kysela
2004-03-31 9:10 ` Russell King
2004-03-31 9:22 ` Jaroslav Kysela
2004-03-31 9:27 ` Russell King
2004-03-31 11:31 ` James Courtier-Dutton
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=20040309104346.C1987@flint.arm.linux.org.uk \
--to=rmk+alsa@arm.linux.org.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=kshitij@ti.com \
--cc=perex@suse.cz \
/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