From owner-freebsd-current Thu Sep 21 17:10:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 863E037B424 for ; Thu, 21 Sep 2000 17:10:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA52850; Thu, 21 Sep 2000 17:11:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009220011.RAA52850@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-reply-to: Your message of "Thu, 21 Sep 2000 17:59:25 MDT." <200009212359.RAA63352@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 17:11:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : >> If I remember from a discussion with John Baldwin, the reason we > : >> don't do this (yet) is that HLT only wakes up when you take an > : >> interrupt, and there are cases where we can't guarantee that we'll > : >> take an interrupt in order to get us out of the HLT. > : > > : >I thought that's what the timer interrupts were for... We can't > : >guarantee that we'll get one? That seems very serious to me. > : > : The problem is that one cpu may wich to schedule a process to run on > : the idle cpu, but it can't because the idle cpu is halted and won't > : wake up until the next irq. > > Since I'm running a UP kernel, that can't happen. Actually, there are pathalogical cases where it could, but they are, well, pathalogical. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message