From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Enable interrupt driven flow control
Date: Fri, 5 Sep 2014 12:11:48 -0700 [thread overview]
Message-ID: <20140905191148.GA24879@kroah.com> (raw)
In-Reply-To: <1409941402-486-1-git-send-email-kys@microsoft.com>
On Fri, Sep 05, 2014 at 11:23:22AM -0700, K. Y. Srinivasan wrote:
> This is a win8 feature that has been implemented. Turn on the feature bit
> to enable the feature.
What does those two sentances even mean?
> With this feature turned on,
What is "this"?
> when the host is waiting
> for space to become available on the ringbuffer (host to guest), the guest
> will interrupt the host when space becomes available (as part of draining
> the ring buffer).
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/hv/ring_buffer.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
> index 15db66b..6361d12 100644
> --- a/drivers/hv/ring_buffer.c
> +++ b/drivers/hv/ring_buffer.c
> @@ -361,6 +361,11 @@ int hv_ringbuffer_init(struct hv_ring_buffer_info *ring_info,
> ring_info->ring_buffer->read_index =
> ring_info->ring_buffer->write_index = 0;
>
> + /*
> + * Set the feature bit for enabling flow control.
> + */
> + ring_info->ring_buffer->feature_bits.value = 1;
What happens if you are running on an old system that doesn't support
this new "feature"?
thanks,
greg k-h
next prev parent reply other threads:[~2014-09-05 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 18:23 [PATCH 1/1] Drivers: hv: vmbus: Enable interrupt driven flow control K. Y. Srinivasan
2014-09-05 19:11 ` Greg KH [this message]
2014-09-05 20:53 ` KY Srinivasan
2014-09-05 21:26 ` Greg KH
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=20140905191148.GA24879@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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