From: "David S. Miller" <davem@redhat.com>
To: Olaf Hering <olh@suse.de>
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: consistent_sync_for_cpu() and friends on ppc32
Date: Mon, 15 Mar 2004 12:36:47 -0800 [thread overview]
Message-ID: <20040315123647.4ce943b7.davem@redhat.com> (raw)
In-Reply-To: <20040315201616.GA31268@suse.de>
On Mon, 15 Mar 2004 21:16:16 +0100
Olaf Hering <olh@suse.de> wrote:
> what is the fix for ppc32? This patch went into Linus tree:
> people/akpm/patches/2.6/2.6.4/2.6.4-mm1/broken-out/dma_sync_for_device-cpu.patch
...
> include/asm/pci.h: In function `pci_dma_sync_single_for_cpu':
Ben, can you work this out? I can make it compile by just making the
_for_cpu and _for_device routines behave identically to what the
consisten_sync{,_page}() stuff does now. But I'd much rather a ppc32
person implement it correctly and optimally.
In short, the _for_device routines should make sure cacheable data in
the cpu is fully visible to the DMA device, and _for_cpu should make
sure all device DMA is visible to the processor.
next prev parent reply other threads:[~2004-03-15 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 20:16 consistent_sync_for_cpu() and friends on ppc32 Olaf Hering
2004-03-15 20:36 ` David S. Miller [this message]
2004-03-15 21:59 ` Benjamin Herrenschmidt
2004-03-16 0:23 ` Benjamin Herrenschmidt
2004-03-16 0:49 ` David S. Miller
2004-03-16 1:36 ` Benjamin Herrenschmidt
2004-03-16 18:46 ` David S. Miller
2004-03-16 21:54 ` Benjamin Herrenschmidt
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=20040315123647.4ce943b7.davem@redhat.com \
--to=davem@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
/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.