From: Jeff Garzik <jeff@garzik.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Colin Tuckley <colin.tuckley@arm.com>
Subject: Re: [PATCH v2] sata_sil24: Use memory barriers before issuing commands
Date: Thu, 10 Jun 2010 16:14:42 -0400 [thread overview]
Message-ID: <4C1147B2.7090207@garzik.org> (raw)
In-Reply-To: <20100610160212.18091.29856.stgit@e102109-lin.cambridge.arm.com>
On 06/10/2010 12:02 PM, Catalin Marinas wrote:
> The data in the cmd_block buffers may reach the main memory after the
> writel() to the device ports. This patch introduces two calls to wmb()
> to ensure the relative ordering.
>
> Signed-off-by: Catalin Marinas<catalin.marinas@arm.com>
> Tested-by: Colin Tuckley<colin.tuckley@arm.com>
> Cc: Tejun Heo<tj@kernel.org>
> Cc: Jeff Garzik<jeff@garzik.org>
> ---
> drivers/ata/sata_sil24.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/ata/sata_sil24.c b/drivers/ata/sata_sil24.c
> index e925051..a5d5aff 100644
> --- a/drivers/ata/sata_sil24.c
> +++ b/drivers/ata/sata_sil24.c
> @@ -622,6 +622,11 @@ static int sil24_exec_polled_cmd(struct ata_port *ap, int pmp,
> irq_enabled = readl(port + PORT_IRQ_ENABLE_SET);
> writel(PORT_IRQ_COMPLETE | PORT_IRQ_ERROR, port + PORT_IRQ_ENABLE_CLR);
>
> + /*
> + * The barrier is required to ensure that writes to cmd_block reach
> + * the memory before the write to PORT_CMD_ACTIVATE.
> + */
> + wmb();
> writel((u32)paddr, port + PORT_CMD_ACTIVATE);
> writel((u64)paddr>> 32, port + PORT_CMD_ACTIVATE + 4);
>
> @@ -895,6 +900,11 @@ static unsigned int sil24_qc_issue(struct ata_queued_cmd *qc)
> paddr = pp->cmd_block_dma + tag * sizeof(*pp->cmd_block);
> activate = port + PORT_CMD_ACTIVATE + tag * 8;
>
> + /*
> + * The barrier is required to ensure that writes to cmd_block reach
> + * the memory before the write to PORT_CMD_ACTIVATE.
> + */
> + wmb();
> writel((u32)paddr, activate);
> writel((u64)paddr>> 32, activate + 4);
>
applied
prev parent reply other threads:[~2010-06-10 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 16:02 [PATCH v2] sata_sil24: Use memory barriers before issuing commands Catalin Marinas
2010-06-10 16:12 ` Tejun Heo
2010-06-10 16:23 ` Catalin Marinas
2010-06-10 16:42 ` Catalin Marinas
2010-06-11 0:43 ` Robert Hancock
2010-06-11 1:38 ` Nick Piggin
2010-06-11 9:16 ` FUJITA Tomonori
2010-06-11 9:41 ` Catalin Marinas
2010-06-11 10:11 ` Nick Piggin
2010-06-11 11:04 ` Catalin Marinas
2010-06-12 1:30 ` Robert Hancock
2010-06-12 1:30 ` Robert Hancock
2010-06-15 11:10 ` Catalin Marinas
2010-06-15 11:10 ` Catalin Marinas
2010-06-15 11:31 ` Nick Piggin
2010-06-19 22:32 ` Catalin Marinas
2010-06-14 0:35 ` FUJITA Tomonori
2010-06-23 13:00 ` Mark Lord
2010-06-10 20:14 ` Jeff Garzik [this message]
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=4C1147B2.7090207@garzik.org \
--to=jeff@garzik.org \
--cc=catalin.marinas@arm.com \
--cc=colin.tuckley@arm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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.