lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 16 May 2008 16:03:25 +0800
From:	Kevin Hao <kexin.hao@...driver.com>
To:	Balaji Rao R <balajirrao@...il.com>
Cc:	venkatesh.pallipadi@...el.com, clemens@...isch.de,
	bob.picco@...com, mingo@...hat.com, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: Get irq for hpet timer

On Fri, 2008-05-16 at 13:23 +0530, Balaji Rao R wrote:
> On Fri, May 16, 2008 at 11:35 AM, Kevin Hao <kexin.hao@...driver.com> wrote:
> >
> > Hi,
> >
> > x86: get irq for hpet timer
> >
> > HPET timer's IRQ is 0 by default, so we have to select which irq
> > will be used for these timers. We wait to set the timer's irq until
> > we really turn on interrupt in order to reduce the chance of
> > conflicting with some legacy device.
> >
> Yes, this is alright. But  i've seen some machines where we have a
> valid IRQ in 'devp->hd_hdwirq' which you should not ignore. So, first
> check if it is zero and only then do a hpet_timer_get_irq.

Yes, I have checked that case in hpet_timer_get_irq function. See the
following code:

+       irq = devp->hd_hdwirq;


+       if (irq) {
+               if (request_irq(irq, hpet_interrupt, irq_flags,
+                               devp->hd_name, (void *)devp)) {
+                       printk(KERN_ERR "hpet: IRQ %d is not free\n",
irq);
+                       irq = 0;
+               }
+               return irq;
+       }

Is that right?

Thanks for your comments.

Best Regards,
Kevin

> 
> --
> warm regards
> 
> Balaji Rao
> NITK Surathkal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ