From: Robert Hancock <hancockrwd@gmail.com>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
DE/ATA development list <linux-ide@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [BUG] bug when enabling VM DEBUG
Date: Tue, 11 May 2010 20:41:29 -0600 [thread overview]
Message-ID: <4BEA1559.9000107@gmail.com> (raw)
In-Reply-To: <AANLkTikoNc6oAY5JthYX1jWx1w2KeJ1fGab72Z-OvIVG@mail.gmail.com>
On 05/11/2010 09:27 AM, saeed bishara wrote:
> Jeff,
> seems that the libata do pio to buffer which was allocated with
> kmalloc, and under arm arch, the flush_dcache_page() is needed to
> prevent cache aliasing, the later function calls the page_mapping
> which falls on PageSlab(page)
>
> as the flush_dcache_page() is needed to prevent aliasing, it can be
> skipped if the page is Slab as such pages are used only by the kernel.
> here a suggested patch:
>
> --- a/drivers/ata/libata-sff.c
> +++ b/drivers/ata/libata-sff.c
> @@ -894,7 +894,7 @@ static void ata_pio_sector(struct ata_queued_cmd *qc)
> do_write);
> }
>
> - if (!do_write)
> + if (!do_write&& !PageSlab(page))
> flush_dcache_page(page);
>
> saeed
I would think that check belongs inside flush_dcache_page itself, rather
than forcing every driver to include it..
next prev parent reply other threads:[~2010-05-12 2:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 13:06 [BUG] bug when enabling VM DEBUG saeed bishara
2010-05-10 13:09 ` saeed bishara
2010-05-11 15:27 ` saeed bishara
2010-05-12 2:41 ` Robert Hancock [this message]
2010-05-12 11:10 ` Catalin Marinas
2010-05-12 11:53 ` Sebastian Andrzej Siewior
2010-05-12 12:24 ` Catalin Marinas
2010-05-12 13:06 ` Jamie Lokier
2010-05-12 23:22 ` Robert Hancock
2010-05-13 11:30 ` Catalin Marinas
2010-05-14 21:48 ` Jeff Garzik
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=4BEA1559.9000107@gmail.com \
--to=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saeed.bishara@gmail.com \
/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).