From: akpm@linux-foundation.org
To: jeff@garzik.org
Cc: linux-ide@vger.kernel.org, akpm@linux-foundation.org,
catalin.marinas@arm.com, jgarzik@pobox.com, stable@kernel.org,
tj@kernel.org
Subject: [patch for 2.6.33? 1/1] ata: call flush_dcache_page() around PIO data transfers in libata-aff.c
Date: Tue, 02 Feb 2010 14:11:08 -0800 [thread overview]
Message-ID: <201002022211.o12MB8cJ017441@imap1.linux-foundation.org> (raw)
From: Catalin Marinas <catalin.marinas@arm.com>
Depending on the direction of the transfer, flush_dcache_page() must be
called either before (ATA_TFLAG_WRITE) or after (!ATA_TFLAG_WRITE) the
data copying to avoid D-cache aliasing with user space or I-D cache
coherency issues (when reading data from an ATA device using PIO, the
kernel dirties the D-cache but there is no flush_dcache_page() required on
Harvard architectures).
This patch allows the ARM boards to use a rootfs on CompactFlash with the
PATA platform driver.
As Anfei Zhou mentioned in a recent patch ("flush dcache before writing
into page to avoid alias"), on some architectures there may be a
performance benefit in differentiating the flush_dcache_page() calls based
on whether the kernel or the user page needs flushing.
IMHO, we should differentiate based on the direction (kernel reading or
writing from/to such page). In the ARM case with PIPT Harvard caches
(newer processors), the kernel reading from a page that may be mapped in
user space shouldn't need cache flushing. The kernel writing to such page
would require D-cache flushing because of coherency with the I-cache.
Currently on ARM, the latter happens in both cases.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/ata/libata-sff.c | 6 ++++++
1 file changed, 6 insertions(+)
diff -puN drivers/ata/libata-sff.c~ata-call-flush_dcache_page-around-pio-data-transfers-in-libata-affc drivers/ata/libata-sff.c
--- a/drivers/ata/libata-sff.c~ata-call-flush_dcache_page-around-pio-data-transfers-in-libata-affc
+++ a/drivers/ata/libata-sff.c
@@ -874,6 +874,9 @@ static void ata_pio_sector(struct ata_qu
DPRINTK("data %s\n", qc->tf.flags & ATA_TFLAG_WRITE ? "write" : "read");
+ if (do_write)
+ flush_dcache_page(page);
+
if (PageHighMem(page)) {
unsigned long flags;
@@ -893,6 +896,9 @@ static void ata_pio_sector(struct ata_qu
do_write);
}
+ if (!do_write)
+ flush_dcache_page(page);
+
qc->curbytes += qc->sect_size;
qc->cursg_ofs += qc->sect_size;
_
next reply other threads:[~2010-02-02 22:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 22:11 akpm [this message]
2010-02-02 22:58 ` [patch for 2.6.33? 1/1] ata: call flush_dcache_page() around PIO data transfers in libata-aff.c James Bottomley
2010-02-02 23:05 ` Andrew Morton
2010-02-02 23:14 ` Jeff Garzik
2010-02-02 23:21 ` James Bottomley
2010-02-02 23:21 ` David Miller
2010-02-02 23:30 ` Alan Cox
2010-02-02 23:32 ` James Bottomley
2010-02-02 23:39 ` David Miller
2010-02-03 10:18 ` Catalin Marinas
2010-02-03 16:40 ` James Bottomley
2010-02-03 17:00 ` Jeff Garzik
2010-02-03 17:06 ` Andrew Morton
2010-02-03 17:15 ` Jeff Garzik
2010-02-03 17:20 ` Andrew Morton
2010-02-03 17:29 ` Jeff Garzik
2010-02-03 17:39 ` James Bottomley
2010-02-04 14:33 ` Catalin Marinas
2010-02-04 15:01 ` James Bottomley
2010-02-04 15:39 ` Catalin Marinas
2010-02-04 21:36 ` James Bottomley
2010-02-03 17:40 ` Alan Cox
2010-02-03 17:46 ` Alan Cox
2010-02-03 17:52 ` Jeff Garzik
2010-02-03 18:00 ` Alan Cox
2010-02-03 18:12 ` Jeff Garzik
2010-02-03 17:49 ` Catalin Marinas
2010-02-03 17:54 ` Jeff Garzik
2010-02-03 17:09 ` David Miller
2010-02-02 23:14 ` James Bottomley
2010-02-03 10:07 ` Catalin Marinas
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=201002022211.o12MB8cJ017441@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=jeff@garzik.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@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 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.