From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 06:39:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3996316A41F for ; Wed, 14 Sep 2005 06:39:20 +0000 (GMT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from comsys.ntu-kpi.kiev.ua (comsys.ntu-kpi.kiev.ua [195.245.194.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37B543D45 for ; Wed, 14 Sep 2005 06:39:16 +0000 (GMT) (envelope-from simon@comsys.ntu-kpi.kiev.ua) Received: from pm514-9.comsys.ntu-kpi.kiev.ua (pm514-9.comsys.ntu-kpi.kiev.ua [10.18.54.109]) (authenticated bits=0) by comsys.ntu-kpi.kiev.ua (8.12.10/8.12.10) with ESMTP id j8E6lC82031286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Sep 2005 09:47:15 +0300 (EEST) Received: by pm514-9.comsys.ntu-kpi.kiev.ua (Postfix, from userid 1000) id 56058115; Wed, 14 Sep 2005 09:36:38 +0300 (EEST) Date: Wed, 14 Sep 2005 09:36:38 +0300 From: Andrey Simonenko To: Zlatan Ibrahimovic Message-ID: <20050914063638.GA258@pm514-9.comsys.ntu-kpi.kiev.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Spam-Status: No, score=-4.5 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on comsys.ntu-kpi.kiev.ua X-Virus-Scanned: ClamAV 0.82/1049/Wed Aug 31 10:19:01 2005 on comsys.ntu-kpi.kiev.ua X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org Subject: Re: clock software interrupt X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2005 06:39:20 -0000 On Sat, Sep 10, 2005 at 09:34:48PM +0200, Zlatan Ibrahimovic wrote: > Hi folks, > I've seen clock software interrupt thread (referring to clk_ithd in > kern/kern_intr.c); watching to manpages I read that priority is used > as vector for that thread. My question is how can I call this software > handler? There's no track in the IDT for the associated handler... > (ia32, for better check see i386/i386/exception.s). The siopoll() function was mentioned in previous answer, but I forgot to continue that sentence. I guess that you need something /sys/dev/sio does with clk_ithd, see in its sources how it adds own handlers to clk_ithd and tty_ithd and schedules these handlers.