mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thor Thayer <thor.thayer@linux.intel.com>
To: Mark Rutland <mark.rutland@arm.com>, linux-kernel@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 02/13] EDAC, altera: kill off ACCESS_ONCE()
Date: Mon, 9 Oct 2017 18:12:10 -0500	[thread overview]
Message-ID: <0b61c449-4aa9-095d-fd83-b177670f3fbb@linux.intel.com> (raw)
In-Reply-To: <1507573730-8083-3-git-send-email-mark.rutland@arm.com>

On 10/09/2017 01:28 PM, Mark Rutland wrote:
> For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
> preference to ACCESS_ONCE(), and new code is expected to use one of the
> former. So far, there's been no reason to change most existing uses of
> ACCESS_ONCE(), as these aren't currently harmful.
> 
> However, for some features it is necessary to instrument reads and
> writes separately, which is not possible with ACCESS_ONCE(). This
> distinction is critical to correct operation.
> 
> It's possible to transform the bulk of kernel code using the Coccinelle
> script below. However, this doesn't handle comments, leaving references
> to ACCESS_ONCE() instances which have been removed. As a preparatory
> step, this patch converts the Altera EDAC code and comments to use
> {READ,WRITE}_ONCE() consistently.
> 
> ----
> virtual patch
> 
> @ depends on patch @
> expression E1, E2;
> @@
> 
> - ACCESS_ONCE(E1) = E2
> + WRITE_ONCE(E1, E2)
> 
> @ depends on patch @
> expression E;
> @@
> 
> - ACCESS_ONCE(E)
> + READ_ONCE(E)
> ----
> 
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Thor Thayer <thor.thayer@linux.intel.com>
> ---
>   drivers/edac/altera_edac.c | 10 +++++-----
>   1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/edac/altera_edac.c b/drivers/edac/altera_edac.c
> index 346c498..11d6419 100644
> --- a/drivers/edac/altera_edac.c
> +++ b/drivers/edac/altera_edac.c
> @@ -175,11 +175,11 @@ static ssize_t altr_sdr_mc_err_inject_write(struct file *file,
>   	/*
>   	 * To trigger the error, we need to read the data back
>   	 * (the data was written with errors above).
> -	 * The ACCESS_ONCE macros and printk are used to prevent the
> +	 * The READ_ONCE macros and printk are used to prevent the
>   	 * the compiler optimizing these reads out.
>   	 */
> -	reg = ACCESS_ONCE(ptemp[0]);
> -	read_reg = ACCESS_ONCE(ptemp[1]);
> +	reg = READ_ONCE(ptemp[0]);
> +	read_reg = READ_ONCE(ptemp[1]);
>   	/* Force Read */
>   	rmb();
>   
> @@ -618,7 +618,7 @@ static ssize_t altr_edac_device_trig(struct file *file,
>   	for (i = 0; i < (priv->trig_alloc_sz / sizeof(*ptemp)); i++) {
>   		/* Read data so we're in the correct state */
>   		rmb();
> -		if (ACCESS_ONCE(ptemp[i]))
> +		if (READ_ONCE(ptemp[i]))
>   			result = -1;
>   		/* Toggle Error bit (it is latched), leave ECC enabled */
>   		writel(error_mask, (drvdata->base + priv->set_err_ofst));
> @@ -635,7 +635,7 @@ static ssize_t altr_edac_device_trig(struct file *file,
>   
>   	/* Read out written data. ECC error caused here */
>   	for (i = 0; i < ALTR_TRIGGER_READ_WRD_CNT; i++)
> -		if (ACCESS_ONCE(ptemp[i]) != i)
> +		if (READ_ONCE(ptemp[i]) != i)
>   			edac_printk(KERN_ERR, EDAC_DEVICE,
>   				    "Read doesn't match written data\n");
>   
> 

Tested on Cyclone5 and Arria10. Thanks!
Acked-by: Thor Thayer <thor.thayer@linux.intel.com>

  reply	other threads:[~2017-10-09 23:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 18:28 [PATCH 00/13] Preparatory work to " Mark Rutland
2017-10-09 18:28 ` [PATCH 01/13] dm integrity: " Mark Rutland
2017-10-09 18:28 ` [PATCH 02/13] EDAC, altera: " Mark Rutland
2017-10-09 23:12   ` Thor Thayer [this message]
2017-10-10  9:30     ` Mark Rutland
2017-10-09 18:28 ` [PATCH 03/13] firmware/ivc: " Mark Rutland
2017-10-09 18:28 ` [PATCH 04/13] fs: dcache: " Mark Rutland
2017-10-09 18:28 ` [PATCH 05/13] fs: ncpfs: " Mark Rutland
2017-10-09 18:28 ` [PATCH 06/13] media: dvb_ringbuffer: " Mark Rutland
2017-10-09 18:28 ` [PATCH 07/13] net: netlink/netfilter: " Mark Rutland
2017-10-09 18:28 ` [PATCH 08/13] net/ipv4/tcp_input.c: " Mark Rutland
2017-10-09 19:03   ` Mark Rutland
2017-10-09 18:28 ` [PATCH 09/13] net: average: " Mark Rutland
2017-10-10  9:28   ` Mark Rutland
2017-10-09 18:28 ` [PATCH 10/13] samples: mic/mpssd/mpssd.c: " Mark Rutland
2017-10-09 18:28 ` [PATCH 11/13] selftests/powerpc: " Mark Rutland
2017-10-10  0:45   ` Michael Ellerman
2017-10-10  9:32     ` Mark Rutland
2017-10-09 18:28 ` [PATCH 12/13] workqueue: " Mark Rutland
2017-10-10 14:06   ` Tejun Heo
2017-10-10 16:21     ` Mark Rutland
2017-10-09 18:28 ` [PATCH 13/13] rcutorture: formal: prepare for ACCESS_ONCE() removal Mark Rutland
2017-10-09 19:51   ` Paul E. McKenney
2017-10-10  9:54     ` Mark Rutland
2017-10-10 12:47       ` Paul E. McKenney
2017-10-10 12:50         ` Mark Rutland
2017-10-10 14:52           ` Paul E. McKenney
2017-10-10 16:24             ` Mark Rutland
2017-10-10 16:35               ` Paul E. McKenney
2017-10-10 16:27             ` Joe Perches
2017-10-10 16:35               ` Paul E. McKenney
2017-10-10 16:41               ` Mark Rutland
2017-10-10 16:57                 ` Joe Perches
2017-10-10 17:06                   ` Mark Rutland
2017-10-09 20:02 ` [PATCH 00/13] Preparatory work to kill off ACCESS_ONCE() Paul E. McKenney

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=0b61c449-4aa9-095d-fd83-b177670f3fbb@linux.intel.com \
    --to=thor.thayer@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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

Powered by JetHome