From owner-freebsd-arch@FreeBSD.ORG Thu Dec 11 17:32:27 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1737216A4CE for ; Thu, 11 Dec 2003 17:32:27 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32AD943D09 for ; Thu, 11 Dec 2003 17:32:26 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc11) with ESMTP id <2003121201322501300c2ujoe>; Fri, 12 Dec 2003 01:32:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA91208; Thu, 11 Dec 2003 17:32:23 -0800 (PST) Date: Thu, 11 Dec 2003 17:32:21 -0800 (PST) From: Julian Elischer To: Nate Lawson In-Reply-To: <20031211170335.X51376@root.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Bruce M Simpson cc: "M. Warner Losh" cc: arch@freebsd.org Subject: Re: Common device driver classes? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 01:32:27 -0000 On Thu, 11 Dec 2003, Nate Lawson wrote: > > Those would definitely be properties of the CPU and could be exported via > sysctl. My need is a little different in that I need to attach a child > driver to a cpu. If I understand what was said.. then I agree that a buss for each CPU's private "drivers", (one bus per cpu) off the root nexus would make sense. One would assume also that PCPU(mybus) would point to the bus, and that each bus would be able to identify it's CPU. The question is how one schedules that control goes to the correct cpu whe you try run that driver as it is likely if it is reading PCPU registers etc. that it can only successfully run on that CPU.