From: Jeff Garzik <jgarzik@pobox.com>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: VDA@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5: ewrk3 cli/sti removal by VDA
Date: Fri, 25 Oct 2002 18:45:04 -0400 [thread overview]
Message-ID: <3DB9C970.3010305@pobox.com> (raw)
In-Reply-To: 20021022020932.GA13818@www.kroptech.com
Adam Kropelin wrote:
>On Mon, Oct 21, 2002 at 08:36:17PM -0400, Jeff Garzik wrote:
>
>
>>Adam Kropelin wrote:
>>
>>
>>>Below is a patch from Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
>>>which
>>>removes cli/sti in the ewrk3 driver. It tests out fine here with SMP &
>>>preempt.
>>>
>>>
>>Applied and then cleaned up... ETHTOOL_PHYS_ID needs to use
>>schedule_timeout(), and using typeof should be avoided.
>>
>>
>
>The patch below (against yours) should fix ETHTOOL_PHYS_ID again. Let me
>know if I got it wrong. Was my prior use of
>wait_event_interruptible_tiumeout actually broken or rather
>just a lot more complicated than it needed to be?
>
>I didn't find any use of typeof. If you point me to it I'll fix that up,
>too.
>
>Thanks for bearing with me. I'm climbing the clue-ladder as fast as I
>can... ;)
>
>--Adam
>
>--- linux-2.5.44/drivers/net/ewrk3.c Mon Oct 21 22:01:01 2002
>+++ linux-2.5.44/drivers/net/ewrk3.c.new Mon Oct 21 21:58:13 2002
>@@ -1759,23 +1759,18 @@
> return 0;
> }
>
>-#ifdef BROKEN
> /* Blink LED for identification */
> case ETHTOOL_PHYS_ID: {
> struct ethtool_value edata;
> u_long flags;
>- long delay, ret;
>+ long ret=0;
> u_char cr;
> int count;
>- wait_queue_head_t wait;
>-
>- init_waitqueue_head(&wait);
>
> if (copy_from_user(&edata, useraddr, sizeof(edata)))
> return -EFAULT;
>
> /* Toggle LED 4x per second */
>- delay = HZ >> 2;
> count = edata.data << 2;
>
> spin_lock_irqsave(&lp->hw_lock, flags);
>@@ -1796,24 +1791,21 @@
>
> /* Wait a little while */
> spin_unlock_irqrestore(&lp->hw_lock, flags);
>- ret = delay;
>- __wait_event_interruptible_timeout(wait, 0, ret);
>+ set_current_state(TASK_INTERRUPTIBLE);
>+ ret = schedule_timeout(HZ>>2);
>
>
close -- if schedule_timeout() returns greater than zero, that number is
the remaining jiffies that schedule_timeout _should_ have slept, but did
not. Ideally you need to call it in a loop, that decrements a variable
based on schedule_timeout return code.
next prev parent reply other threads:[~2002-10-25 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 2:13 [PATCH] 2.5: ewrk3 cli/sti removal by VDA Adam Kropelin
2002-10-19 2:46 ` Adam Kropelin
2002-10-19 14:55 ` Denis Vlasenko
2002-10-22 0:36 ` Jeff Garzik
2002-10-22 2:09 ` Adam Kropelin
2002-10-22 2:16 ` Jeff Garzik
2002-10-25 22:45 ` Jeff Garzik [this message]
2002-10-25 22:54 ` Adam Kropelin
2002-11-01 21:17 ` Adam Kropelin
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=3DB9C970.3010305@pobox.com \
--to=jgarzik@pobox.com \
--cc=VDA@port.imtp.ilyichevsk.odessa.ua \
--cc=akropel1@rochester.rr.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.