[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180129072050.GA3575@kroah.com>
Date: Mon, 29 Jan 2018 08:20:50 +0100
From: Greg KH <greg@...ah.com>
To: "Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
KY Srinivasan <kys@...rosoft.com>
Subject: Re: [PATCH v3 char-misc 1/1] Drivers: hv: vmbus: Implement Direct
Mode for stimer0
On Sun, Jan 28, 2018 at 09:06:48PM +0000, Michael Kelley (EOSG) wrote:
> From: Michael Kelley <mikelley@...rosoft.com>
>
> The 2016 version of Hyper-V offers the option to operate the guest VM
> per-vcpu stimer's in Direct Mode, which means the timer interupts on its
> own vector rather than queueing a VMbus message. Direct Mode reduces
> timer processing overhead in both the hypervisor and the guest, and
> avoids having timer interrupts pollute the VMbus interrupt stream for
> the synthetic NIC and storage. This patch enables Direct Mode by
> default on stimer0 when running on a version of Hyper-V that supports it,
> with a hv_vmbus module parameter for disabling Direct Mode and reverting
> to the old behavior.
You didn't change the text here as there is no more module parameter :(
> --- a/drivers/hv/hv.c
> +++ b/drivers/hv/hv.c
> @@ -27,8 +27,9 @@
> #include <linux/vmalloc.h>
> #include <linux/hyperv.h>
> #include <linux/version.h>
> -#include <linux/interrupt.h>
> +#include <linux/random.h>
> #include <linux/clockchips.h>
> +#include <linux/module.h>
Still need this .h file?
thanks,
greg k-h
Powered by blists - more mailing lists