mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KY Srinivasan <kys@microsoft.com>
To: Jason Wang <jasowang@redhat.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Greg KH (gregkh@linuxfoundation.org)"
	<gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH] drivers: hv: switch to use mb() instead of smp_mb()
Date: Tue, 18 Jun 2013 12:58:08 +0000	[thread overview]
Message-ID: <572dfd2a52484936b598e50f29e99beb@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <1371531863-12491-1-git-send-email-jasowang@redhat.com>



> -----Original Message-----
> From: Jason Wang [mailto:jasowang@redhat.com]
> Sent: Tuesday, June 18, 2013 1:04 AM
> To: KY Srinivasan; Haiyang Zhang; devel@linuxdriverproject.org; linux-
> kernel@vger.kernel.org
> Cc: Jason Wang; stable@vger.kernel.org
> Subject: [PATCH] drivers: hv: switch to use mb() instead of smp_mb()
> 
> Even if guest were compiled without SMP support, it could not assume that host
> wasn't. So switch to use mb() instead of smp_mb() to force memory barriers for
> UP guest.
> 
> Cc: K. Y. Srinivasan <kys@microsoft.com>
> Cc: Haiyang Zhang <haiyangz@microsoft.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>

> ---
>  drivers/hv/ring_buffer.c |   10 +++++-----
>  drivers/hv/vmbus_drv.c   |    2 +-
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
> index d6fbb57..791f45d 100644
> --- a/drivers/hv/ring_buffer.c
> +++ b/drivers/hv/ring_buffer.c
> @@ -32,7 +32,7 @@
>  void hv_begin_read(struct hv_ring_buffer_info *rbi)
>  {
>  	rbi->ring_buffer->interrupt_mask = 1;
> -	smp_mb();
> +	mb();
>  }
> 
>  u32 hv_end_read(struct hv_ring_buffer_info *rbi)
> @@ -41,7 +41,7 @@ u32 hv_end_read(struct hv_ring_buffer_info *rbi)
>  	u32 write;
> 
>  	rbi->ring_buffer->interrupt_mask = 0;
> -	smp_mb();
> +	mb();
> 
>  	/*
>  	 * Now check to see if the ring buffer is still empty.
> @@ -71,7 +71,7 @@ u32 hv_end_read(struct hv_ring_buffer_info *rbi)
> 
>  static bool hv_need_to_signal(u32 old_write, struct hv_ring_buffer_info *rbi)
>  {
> -	smp_mb();
> +	mb();
>  	if (rbi->ring_buffer->interrupt_mask)
>  		return false;
> 
> @@ -442,7 +442,7 @@ int hv_ringbuffer_write(struct hv_ring_buffer_info
> *outring_info,
>  					     sizeof(u64));
> 
>  	/* Issue a full memory barrier before updating the write index */
> -	smp_mb();
> +	mb();
> 
>  	/* Now, update the write location */
>  	hv_set_next_write_location(outring_info, next_write_location);
> @@ -549,7 +549,7 @@ int hv_ringbuffer_read(struct hv_ring_buffer_info
> *inring_info, void *buffer,
>  	/* Make sure all reads are done before we update the read index since
> */
>  	/* the writer may start writing to the read area once the read index */
>  	/*is updated */
> -	smp_mb();
> +	mb();
> 
>  	/* Update the read index */
>  	hv_set_next_read_location(inring_info, next_read_location);
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index bf421e0..4004e54 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -434,7 +434,7 @@ static void vmbus_on_msg_dpc(unsigned long data)
>  		 * will not deliver any more messages since there is
>  		 * no empty slot
>  		 */
> -		smp_mb();
> +		mb();
> 
>  		if (msg->header.message_flags.msg_pending) {
>  			/*
> --
> 1.7.1
> 
> 



      reply	other threads:[~2013-06-18 12:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18  5:04 Jason Wang
2013-06-18 12:58 ` KY Srinivasan [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=572dfd2a52484936b598e50f29e99beb@SN2PR03MB061.namprd03.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®