From: Greg KH <gregkh@suse.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
virtualization@lists.osdl.org,
Haiyang Zhang <haiyangz@microsoft.com>,
Hank Janssen <hjanssen@microsoft.com>
Subject: Re: [PATCH ]:Staging: hv: Allocate the vmbus irq dynamically
Date: Tue, 15 Feb 2011 07:59:54 -0800 [thread overview]
Message-ID: <20110215155954.GA32313@suse.de> (raw)
In-Reply-To: <1297782937-24082-1-git-send-email-kys@microsoft.com>
On Tue, Feb 15, 2011 at 07:15:37AM -0800, K. Y. Srinivasan wrote:
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> Signed-off-by: Hank Janssen <hjanssen@microsoft.com>
>
> ---
> drivers/staging/hv/vmbus_drv.c | 49 +++++++++++++++++++++++++++------------
> 1 files changed, 34 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/staging/hv/vmbus_drv.c b/drivers/staging/hv/vmbus_drv.c
> index 459c707..f279e6a 100644
> --- a/drivers/staging/hv/vmbus_drv.c
> +++ b/drivers/staging/hv/vmbus_drv.c
> @@ -36,9 +36,7 @@
> #include "vmbus_private.h"
>
>
> -/* FIXME! We need to do this dynamically for PIC and APIC system */
> -#define VMBUS_IRQ 0x5
> -#define VMBUS_IRQ_VECTOR IRQ5_VECTOR
> +static int vmbus_irq;
>
> /* Main vmbus driver data structure */
> struct vmbus_driver_context {
> @@ -57,6 +55,25 @@ struct vmbus_driver_context {
> struct vm_device device_ctx;
> };
>
> +/*
> + * Find an un-used IRQ that the VMBUS can use. If none is available; return -1.
> + */
> +
> +static int vmbus_get_irq(void)
No extra blank line between function comment and function.
> +{
> + unsigned int avail_irq_mask;
> + int irq = -1;
> + /*
Put an extra blank line after your variables please.
> + * Pick the first unused interrupt. HyperV can
> + * interrupt us on any interrupt line we specify.
> + */
> + avail_irq_mask = probe_irq_on();
> + if (avail_irq_mask != 0)
> + irq = ffs(avail_irq_mask);
> + probe_irq_off(avail_irq_mask);
> + return irq;
> +}
> +
> static int vmbus_match(struct device *device, struct device_driver *driver);
> static int vmbus_probe(struct device *device);
> static int vmbus_remove(struct device *device);
> @@ -80,7 +97,6 @@ EXPORT_SYMBOL(vmbus_loglevel);
> /* (ALL_MODULES << 16 | DEBUG_LVL_ENTEREXIT); */
> /* (((VMBUS | VMBUS_DRV)<<16) | DEBUG_LVL_ENTEREXIT); */
>
> -static int vmbus_irq = VMBUS_IRQ;
>
> /* Set up per device attributes in /sys/bus/vmbus/devices/<bus device> */
> static struct device_attribute vmbus_device_attrs[] = {
> @@ -466,7 +482,7 @@ static int vmbus_bus_init(void)
> struct hv_driver *driver = &vmbus_drv.drv_obj;
> struct vm_device *dev_ctx = &vmbus_drv.device_ctx;
> int ret;
> - unsigned int vector;
> + unsigned int vector, prev_irq = ~0;
>
> DPRINT_INFO(VMBUS, "+++++++ HV Driver version = %s +++++++",
> HV_DRV_VERSION);
> @@ -518,19 +534,23 @@ static int vmbus_bus_init(void)
> }
>
> /* Get the interrupt resource */
> - ret = request_irq(vmbus_irq, vmbus_isr, IRQF_SAMPLE_RANDOM,
> - driver->name, NULL);
> -
> - if (ret != 0) {
> - DPRINT_ERR(VMBUS_DRV, "ERROR - Unable to request IRQ %d",
> - vmbus_irq);
> -
> +get_irq_again:
> + vmbus_irq = vmbus_get_irq();
> + if ((vmbus_irq < 0) || (prev_irq == vmbus_irq)) {
> + printk(KERN_WARNING "VMBUS_DRV: Failed to allocate IRQ\n");
> bus_unregister(&vmbus_drv_ctx->bus);
> -
> ret = -1;
Please provide a "real" error code.
> goto cleanup;
> }
> - vector = VMBUS_IRQ_VECTOR;
> + prev_irq = vmbus_irq;
> +
> + ret = request_irq(vmbus_irq, vmbus_isr, IRQF_SAMPLE_RANDOM,
> + driver->name, NULL);
> +
> + if (ret != 0)
> + goto get_irq_again;
You just set up the potential for an endless loop. You almost _never_
want to goto backwards in a function. Please don't do this.
> +
> + vector = IRQ0_VECTOR + vmbus_irq;
What's this for?
> DPRINT_INFO(VMBUS_DRV, "irq 0x%x vector 0x%x", vmbus_irq, vector);
And why are you still printing this out for the whole world to see?
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-15 15:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 15:15 [PATCH ]:Staging: hv: Allocate the vmbus irq dynamically K. Y. Srinivasan
2011-02-15 15:59 ` Greg KH [this message]
2011-02-15 16:53 ` KY Srinivasan
2011-02-15 16:59 ` Hank Janssen
2011-02-15 17:22 ` Greg KH
2011-02-15 17:28 ` Hank Janssen
2011-02-15 19:09 ` Hank Janssen
2011-02-15 19:33 ` Greg KH
2011-02-15 17:25 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2011-02-15 19:55 [PATCH]: Staging: " K. Y. Srinivasan
2011-02-18 21:14 ` Greg KH
2011-02-18 22:00 ` KY Srinivasan
2011-02-18 22:07 ` Greg KH
2011-02-18 22:16 ` KY Srinivasan
2011-02-18 22:29 ` Greg KH
2011-02-19 0:56 ` KY Srinivasan
2011-02-19 1:02 ` Greg KH
2011-02-19 1:19 ` KY Srinivasan
2011-02-19 10:23 ` Thomas Gleixner
2011-02-19 14:34 ` KY Srinivasan
2011-02-19 15:12 ` Thomas Gleixner
2011-02-19 16:46 ` KY Srinivasan
2011-02-20 16:15 ` Thomas Gleixner
2011-02-21 3:43 ` KY Srinivasan
2011-02-21 3:50 ` Greg KH
2011-02-21 11:02 ` Thomas Gleixner
2011-02-21 14:40 ` KY Srinivasan
2011-02-21 14:51 ` Thomas Gleixner
2011-02-21 15:43 ` Greg KH
2011-02-23 19:16 ` Greg KH
2011-02-23 19:22 ` KY Srinivasan
2011-02-19 1:26 K. Y. Srinivasan
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=20110215155954.GA32313@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).