public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Studierende der Universitaet des Saarlandes  <masp0008@stud.uni-sb.de>
To: Tim Hockin <thockin@sun.com>,
	linux-kernel@vger.kernel.org, manfred@colorfullife.com,
	manfred@colorfullife.com
Subject: Re: [PATCH]  sym53c8xx timer rework
Date: Tue, 10 Jul 2001 09:48:27 +0000	[thread overview]
Message-ID: <3B4ACF6B.5F194E54@stud.uni-saarland.de> (raw)

>  /*
> -**     Stop the ncr_timeout process
> -**     Set release_stage to 1 and wait that ncr_timeout() set it to 2.
> +**     Stop the ncr_timeout process - lock it to ensure no timer is running
> +**     on a different CPU, or anything
>  */
> -       np->release_stage = 1;
> -       for (i = 50 ; i && np->release_stage != 2 ; i--) MDELAY (100);
> -       if (np->release_stage != 2)
> -               printk("%s: the timer seems to be already stopped\n",
> -                       ncr_name(np));
> -       else np->release_stage = 2;
> +       NCR_LOCK_NCB(np, flags);
> +       del_timer(&np->timer);
> +       NCR_UNLOCK_NCB(np, flags);

I'm only reading the diff, but this change looks wrong.
The simplest solution is del_timer_sync() instead of
LOCK;del_timer;UNLOCK.

Why do you acqurie the NCB spinlock? the _timeout function runs without
it.

--	
	Manfred

             reply	other threads:[~2001-07-10  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10  9:48 Studierende der Universitaet des Saarlandes [this message]
2001-07-10 18:21 ` [PATCH] sym53c8xx timer rework Tim Hockin
  -- strict thread matches above, loose matches on Subject: below --
2001-07-10  7:19 Tim Hockin
2001-07-10 19:00 ` Gérard Roudier

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=3B4ACF6B.5F194E54@stud.uni-saarland.de \
    --to=masp0008@stud.uni-sb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=thockin@sun.com \
    /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