From owner-freebsd-hackers@FreeBSD.ORG  Sat Oct  1 10:00:23 2011
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B93B8106564A;
	Sat,  1 Oct 2011 10:00:23 +0000 (UTC)
	(envelope-from adrian.chadd@gmail.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
	[209.85.212.54])
	by mx1.freebsd.org (Postfix) with ESMTP id A86708FC08;
	Sat,  1 Oct 2011 10:00:19 +0000 (UTC)
Received: by vws11 with SMTP id 11so2663399vws.13
	for <multiple recipients>; Sat, 01 Oct 2011 03:00:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	bh=hUQY13k9yeyUBgrR2cegkNoNQfO0v1KThN2istHVYXc=;
	b=tHFAjUwP94u4MvI18cDJcIVKUnIvqj9cu4JW9TivhdjnMcPyT6P6RvSEeN9kNMKQO+
	xCI1a7M3a5W2iRYt4/E9OlkvlYsjhODlEvPN8tzuGW25wu8CH4T2XQUYUSIYrMw4qu9C
	VDRrW24acNQafCJmm4y63Eki39sWeQfQ5weEM=
MIME-Version: 1.0
Received: by 10.52.72.9 with SMTP id z9mr7844043vdu.60.1317463218655; Sat, 01
	Oct 2011 03:00:18 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.52.161.138 with HTTP; Sat, 1 Oct 2011 03:00:18 -0700 (PDT)
In-Reply-To: <4E86E20B.7000703@FreeBSD.org>
References: <CAJ-Vmoksy68YmTXAQ1S87-+FMUHjZ-K0TOV0OUm3hQpYGZhXHw@mail.gmail.com>
	<4E86DC86.3040204@FreeBSD.org>
	<CAJ-Vmon1xMpourX1u6+x=Y+pi3G3VNCCJRoO1wHH6kCMKFYKog@mail.gmail.com>
	<4E86E20B.7000703@FreeBSD.org>
Date: Sat, 1 Oct 2011 18:00:18 +0800
X-Google-Sender-Auth: M_xHvYdIu90s2bQVscraV06phVI
Message-ID: <CAJ-VmomqBRqeoS3iJiGULmj7xLAO9WeTiqtnYvDSGkZ9nECN2A@mail.gmail.com>
From: Adrian Chadd <adrian@freebsd.org>
To: Alexander Motin <mav@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-hackers@freebsd.org
Subject: Re: how are callouts handled in cpu_idle() ?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Oct 2011 10:00:23 -0000

Right. Hm, what about for i386/amd64 cases we call intr_disable()
before the critical_enter and idleclock, then re-enable either just
before the wait/halt call (like it is now) or just after the
sched_running check (just like it is now.)

That way a filter handler which schedules a callout gets called correctly?


Adrian