From owner-freebsd-arch@FreeBSD.ORG Mon Oct 12 11:06:50 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2716C1065696 for ; Mon, 12 Oct 2009 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 65D718FC13 for ; Mon, 12 Oct 2009 11:06:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9CB6m7O036310 for ; Mon, 12 Oct 2009 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9CB6lJk036306 for freebsd-arch@FreeBSD.org; Mon, 12 Oct 2009 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Oct 2009 11:06:47 GMT Message-Id: <200910121106.n9CB6lJk036306@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-arch@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2009 11:06:50 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/120749 arch [request] Suggest upping the default kern.ps_arg_cache 1 problem total. From owner-freebsd-arch@FreeBSD.ORG Tue Oct 13 21:25:11 2009 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D98F61065672; Tue, 13 Oct 2009 21:25:11 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 813F38FC1E; Tue, 13 Oct 2009 21:25:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n9DHYfEQ009100; Tue, 13 Oct 2009 11:34:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 13 Oct 2009 11:34:51 -0600 (MDT) Message-Id: <20091013.113451.2056345767.imp@bsdimp.com> To: gonzo@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200910130043.n9D0hVCr089970@svn.freebsd.org> References: <200910130043.n9D0hVCr089970@svn.freebsd.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org Subject: Re: svn commit: r198009 - projects/mips/sbin X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 21:25:11 -0000 In message: <200910130043.n9D0hVCr089970@svn.freebsd.org> Oleksandr Tymoshenko writes: : Log: : - Enable fdisk build for MIPS ... : +.if ${MACHINE_ARCH} == "mips" : +_fdisk= fdisk : +.endif : + I'm starting to think that the right answer here is to enable fdisk for all platforms. Warner From owner-freebsd-arch@FreeBSD.ORG Tue Oct 13 21:49:01 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C0EC10656A4 for ; Tue, 13 Oct 2009 21:49:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6188FC1C for ; Tue, 13 Oct 2009 21:49:01 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C59A846B2C for ; Tue, 13 Oct 2009 17:49:00 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 0C9168A01F for ; Tue, 13 Oct 2009 17:49:00 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Date: Tue, 13 Oct 2009 17:48:57 -0400 User-Agent: KMail/1.9.7 References: <200909301732.20589.jhb@freebsd.org> In-Reply-To: <200909301732.20589.jhb@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200910131748.57945.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 13 Oct 2009 17:49:00 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 21:49:01 -0000 On Wednesday 30 September 2009 5:32:20 pm John Baldwin wrote: > A few folks have asked recently for the ability to add descriptive strings to > registered interrupt handlers. This is especially true since the advent of > MSI with multiple interrupts per device. I hacked up a prototype today that > adds a new 'bus_describe_intr()' that takes the IRQ resource, the void * > cookie returned by bus_setup_intr() and var args description and appends that > to the interrupt name in the thread and vmstat -i info. The current patch > only has the MI bits and the MD bits for amd64 as well as a sample change to > the igb(4) driver. > > The patch is at http://www.FreeBSD.org/~jhb/patches/intr_describe.patch. > > An example from this patch is: > > > vmstat -i > interrupt total rate > irq1: atkbd0 8 0 > irq4: uart0 751 5 > irq6: fdc0 6 0 > irq14: ata0 36 0 > irq20: uhci0 20 0 > irq23: uhci3 ehci0 2 0 > irq28: mpt0 1661 11 > irq256: igb0:tx 0 880 6 > irq257: igb0:rx 0 1098 7 > irq258: igb0:link 3 0 > irq259: igb1:tx 0 1 0 > irq260: igb1:rx 0 134 0 > irq261: igb1:link 3 0 Do folks feel that the issues with the intrnames and intrcnt API warrant delaying this work, or do folks have any objections to the proposed bus_describe_intr() API? Personally I think that intrnames and intrcnt are certainly broken, but that they have been broken for quite a while and that these changes do not make them more broken than they currently are. Also, I think that any fixes to intrcnt/intrnames would be orthogonal to bus_describe_intr(). -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Tue Oct 13 22:10:55 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 272061065670 for ; Tue, 13 Oct 2009 22:10:55 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outS.internet-mail-service.net (outs.internet-mail-service.net [216.240.47.242]) by mx1.freebsd.org (Postfix) with ESMTP id 0DC758FC12 for ; Tue, 13 Oct 2009 22:10:55 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id D1215CD3A7; Tue, 13 Oct 2009 15:10:54 -0700 (PDT) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 8B14B2D6019; Tue, 13 Oct 2009 15:10:54 -0700 (PDT) Message-ID: <4AD4FAF1.1060609@elischer.org> Date: Tue, 13 Oct 2009 15:10:57 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: John Baldwin References: <200909301732.20589.jhb@freebsd.org> <200910131748.57945.jhb@freebsd.org> In-Reply-To: <200910131748.57945.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 22:10:55 -0000 John Baldwin wrote: > On Wednesday 30 September 2009 5:32:20 pm John Baldwin wrote: >> A few folks have asked recently for the ability to add descriptive strings > to >> registered interrupt handlers. This is especially true since the advent of >> MSI with multiple interrupts per device. I hacked up a prototype today that >> adds a new 'bus_describe_intr()' that takes the IRQ resource, the void * >> cookie returned by bus_setup_intr() and var args description and appends > that >> to the interrupt name in the thread and vmstat -i info. The current patch >> only has the MI bits and the MD bits for amd64 as well as a sample change to >> the igb(4) driver. >> >> The patch is at http://www.FreeBSD.org/~jhb/patches/intr_describe.patch. >> >> An example from this patch is: >> >>> vmstat -i >> interrupt total rate >> irq1: atkbd0 8 0 >> irq4: uart0 751 5 >> irq6: fdc0 6 0 >> irq14: ata0 36 0 >> irq20: uhci0 20 0 >> irq23: uhci3 ehci0 2 0 >> irq28: mpt0 1661 11 >> irq256: igb0:tx 0 880 6 >> irq257: igb0:rx 0 1098 7 >> irq258: igb0:link 3 0 >> irq259: igb1:tx 0 1 0 >> irq260: igb1:rx 0 134 0 >> irq261: igb1:link 3 0 > > Do folks feel that the issues with the intrnames and intrcnt API warrant > delaying this work, or do folks have any objections to the proposed > bus_describe_intr() API? Personally I think that intrnames and intrcnt are > certainly broken, but that they have been broken for quite a while and that > these changes do not make them more broken than they currently are. Also, I > think that any fixes to intrcnt/intrnames would be orthogonal to > bus_describe_intr(). > I see that in linux this information is available in /proc/(mumble) and people use it. I see no real reason that we should stop this work. From owner-freebsd-arch@FreeBSD.ORG Tue Oct 13 22:40:19 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F2871065672 for ; Tue, 13 Oct 2009 22:40:19 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id ACC868FC08 for ; Tue, 13 Oct 2009 22:40:18 +0000 (UTC) Received: by ewy18 with SMTP id 18so4282492ewy.43 for ; Tue, 13 Oct 2009 15:40:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=aMn18uzNMMVv2X1EcsiPqZI86EMTvTNNm7LyA+SX7tI=; b=FrhyNbPX0nsRVU7hGDY73rhENXcU3U8Ff370ga+TCS+eG+s7k4eEtKEZCMj67v3pbR hM0Vq8M8GyjfqPVqkFFyExsq5EDk1MrfXUAhas4iqBsjnkD3Jv9tJ0e4r9vkmCYgyu6G HoSLrxZ0qNyqL2UrKxvYsqOmewNWZ5LTgZw5M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LFD9PtZ/vJgPUXqezKq58Aj8yXTPLaZqVWuk4znwSx3rGxlbmR2rNXVLBhB+FtWzHu HkAxs0egct5UAIhttbVzCoc4+E37fTNHTI/F6thBhWOGDTAWK86gIkUjUNy1RkCSZPvt Tey/I2seAtUBMRPB6etXWERKMlgB8qHfj1VE8= MIME-Version: 1.0 Received: by 10.216.87.136 with SMTP id y8mr533726wee.43.1255471620694; Tue, 13 Oct 2009 15:07:00 -0700 (PDT) In-Reply-To: <200910131748.57945.jhb@freebsd.org> References: <200909301732.20589.jhb@freebsd.org> <200910131748.57945.jhb@freebsd.org> Date: Tue, 13 Oct 2009 15:07:00 -0700 Message-ID: <2a41acea0910131507l3a50b68u698d876e96880266@mail.gmail.com> From: Jack Vogel To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-arch@freebsd.org Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 22:40:19 -0000 On Tue, Oct 13, 2009 at 2:48 PM, John Baldwin wrote: > On Wednesday 30 September 2009 5:32:20 pm John Baldwin wrote: > > A few folks have asked recently for the ability to add descriptive > strings > to > > registered interrupt handlers. This is especially true since the advent > of > > MSI with multiple interrupts per device. I hacked up a prototype today > that > > adds a new 'bus_describe_intr()' that takes the IRQ resource, the void * > > cookie returned by bus_setup_intr() and var args description and appends > that > > to the interrupt name in the thread and vmstat -i info. The current > patch > > only has the MI bits and the MD bits for amd64 as well as a sample change > to > > the igb(4) driver. > > > > The patch is at http://www.FreeBSD.org/~jhb/patches/intr_describe.patch > . > > > > An example from this patch is: > > > > > vmstat -i > > interrupt total rate > > irq1: atkbd0 8 0 > > irq4: uart0 751 5 > > irq6: fdc0 6 0 > > irq14: ata0 36 0 > > irq20: uhci0 20 0 > > irq23: uhci3 ehci0 2 0 > > irq28: mpt0 1661 11 > > irq256: igb0:tx 0 880 6 > > irq257: igb0:rx 0 1098 7 > > irq258: igb0:link 3 0 > > irq259: igb1:tx 0 1 0 > > irq260: igb1:rx 0 134 0 > > irq261: igb1:link 3 0 > > Do folks feel that the issues with the intrnames and intrcnt API warrant > delaying this work, or do folks have any objections to the proposed > bus_describe_intr() API? Personally I think that intrnames and intrcnt are > certainly broken, but that they have been broken for quite a while and that > these changes do not make them more broken than they currently are. Also, > I > think that any fixes to intrcnt/intrnames would be orthogonal to > bus_describe_intr(). > > I'm in favor of going with what you've done, and let fixes or changes happen later, having this functionality now would be really nice. Jack From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 00:32:34 2009 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0684D106566C for ; Wed, 14 Oct 2009 00:32:34 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7D8318FC1B for ; Wed, 14 Oct 2009 00:32:33 +0000 (UTC) Received: from c122-107-125-150.carlnfd1.nsw.optusnet.com.au (c122-107-125-150.carlnfd1.nsw.optusnet.com.au [122.107.125.150]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n9E0WP8I026922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Oct 2009 11:32:27 +1100 Date: Wed, 14 Oct 2009 11:32:25 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: "M. Warner Losh" In-Reply-To: <20091013.113451.2056345767.imp@bsdimp.com> Message-ID: <20091014103634.A6350@delplex.bde.org> References: <200910130043.n9D0hVCr089970@svn.freebsd.org> <20091013.113451.2056345767.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: gonzo@FreeBSD.org, arch@FreeBSD.org Subject: Re: svn commit: r198009 - projects/mips/sbin X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 00:32:34 -0000 On Tue, 13 Oct 2009, M. Warner Losh wrote: > In message: <200910130043.n9D0hVCr089970@svn.freebsd.org> > Oleksandr Tymoshenko writes: > : Log: > : - Enable fdisk build for MIPS > > I'm starting to think that the right answer here is to enable fdisk > for all platforms. Of course. fdisk is MI except for bugs in it. It should be usable on any system to manage disks or disk images created on any system that needs it natively. fdisk certainly has bugs like assuming that the host system byte order is the same as the target system byte order. It fails on big-endian systems because the target system byte order is always little-endian. Its device independence was broken using g_device_path() just over 1 year ago, so it no longer works on disk images (except possibly if. Older geom breakage is still handled benignly by not aborting when fdisk is run on a system or file that doesn't support geom ioctls (it even has a comment about this, but g_device_path() fails long before the working code is reached). Bruce From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 07:41:08 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9860E106568D for ; Wed, 14 Oct 2009 07:41:08 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 276238FC13 for ; Wed, 14 Oct 2009 07:41:07 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 22so195988fge.13 for ; Wed, 14 Oct 2009 00:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=QsbZPjNBo1VxDLb6rIEzPMgADnv4SSKqC4eUWeoenpU=; b=X/xo9BhD7g+C3MsAAQB/fZUHnUf0zvazncSpinBHWUvJjrh3qOP87MHoA/8R3n4HAY XTSSyTMZBubICJR4uCm+Uhq8vaQ3yCqpNIo9aLLpNDzf73d/pNRsDaTxm6rtV429pJM0 sSfCcnR0obfWzyECW/Fu708uWrja9ZXTerQsA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ko7YZlg6A8b0Zr0uYHdPIppKoofjSzsRNftMzHKAmc2CIXTVamzgRT38TapOqPtXuE Bl2CiAuzH00xCrRYEJYwYoMOPI/M48IqfLgUlQc44HDpMjXVIWSQfiwHbQD11620T6W8 58KAM5s1aDs8vKeE+aTf9FTm0hOO5JlehGSe0= Received: by 10.102.177.33 with SMTP id z33mr3431601mue.87.1255504687642; Wed, 14 Oct 2009 00:18:07 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 23sm1379429mum.14.2009.10.14.00.18.06 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Oct 2009 00:18:07 -0700 (PDT) Sender: Alexander Motin Message-ID: <4AD57B2C.8070606@FreeBSD.org> Date: Wed, 14 Oct 2009 10:18:04 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: John Baldwin References: <200909301732.20589.jhb@freebsd.org> <1255483383.00172964.1255470604@10.7.7.3> In-Reply-To: <1255483383.00172964.1255470604@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 07:41:08 -0000 John Baldwin wrote: > On Wednesday 30 September 2009 5:32:20 pm John Baldwin wrote: >> A few folks have asked recently for the ability to add descriptive strings > to >> registered interrupt handlers. This is especially true since the advent of >> MSI with multiple interrupts per device. I hacked up a prototype today that >> adds a new 'bus_describe_intr()' that takes the IRQ resource, the void * >> cookie returned by bus_setup_intr() and var args description and appends > that >> to the interrupt name in the thread and vmstat -i info. The current patch >> only has the MI bits and the MD bits for amd64 as well as a sample change to >> the igb(4) driver. >> >> The patch is at http://www.FreeBSD.org/~jhb/patches/intr_describe.patch. >> >> An example from this patch is: >> >>> vmstat -i >> interrupt total rate >> irq1: atkbd0 8 0 >> irq4: uart0 751 5 >> irq6: fdc0 6 0 >> irq14: ata0 36 0 >> irq20: uhci0 20 0 >> irq23: uhci3 ehci0 2 0 >> irq28: mpt0 1661 11 >> irq256: igb0:tx 0 880 6 >> irq257: igb0:rx 0 1098 7 >> irq258: igb0:link 3 0 >> irq259: igb1:tx 0 1 0 >> irq260: igb1:rx 0 134 0 >> irq261: igb1:link 3 0 > > Do folks feel that the issues with the intrnames and intrcnt API warrant > delaying this work, or do folks have any objections to the proposed > bus_describe_intr() API? Personally I think that intrnames and intrcnt are > certainly broken, but that they have been broken for quite a while and that > these changes do not make them more broken than they currently are. Also, I > think that any fixes to intrcnt/intrnames would be orthogonal to > bus_describe_intr(). Just some 50 cents on topic: it would be nice if `vmstat -i` was able to show all (more then 2) consumers of shared interrupt instead of "cbb0 wpi0+". I haven't looked who actually limit this and why, so it's just a wish. -- Alexander Motin From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 08:12:16 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 383C8106568B; Wed, 14 Oct 2009 08:12:16 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id AF39F8FC08; Wed, 14 Oct 2009 08:12:15 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n9E8Bv85063959; Wed, 14 Oct 2009 10:12:13 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n9E8BvKk063958; Wed, 14 Oct 2009 10:11:57 +0200 (CEST) (envelope-from olli) Date: Wed, 14 Oct 2009 10:11:57 +0200 (CEST) Message-Id: <200910140811.n9E8BvKk063958@lurza.secnetix.de> From: Oliver Fromme To: freebsd-arch@FreeBSD.ORG, jhb@FreeBSD.ORG, mav@FreeBSD.ORG In-Reply-To: <4AD57B2C.8070606@FreeBSD.org> X-Newsgroups: list.freebsd-arch User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 14 Oct 2009 10:12:13 +0200 (CEST) Cc: Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 08:12:16 -0000 Alexander Motin wrote: > John Baldwin wrote: > > Do folks feel that the issues with the intrnames and intrcnt API warrant > > delaying this work, or do folks have any objections to the proposed > > bus_describe_intr() API? Personally I think that intrnames and intrcnt are > > certainly broken, but that they have been broken for quite a while and that > > these changes do not make them more broken than they currently are. Also, I > > think that any fixes to intrcnt/intrnames would be orthogonal to > > bus_describe_intr(). > > Just some 50 cents on topic: it would be nice if `vmstat -i` was able to > show all (more then 2) consumers of shared interrupt instead of "cbb0 > wpi0+". I haven't looked who actually limit this and why, so it's just a > wish. Here's a whole-hearted "me too". I also often have output like this from vmstat: irq18: ohci2 ohci+ It doesn't even display the number of the second ohci device on irq18. So I always have to grep through /var/run/dmegs.boot to find out the real list of devices, which is annoying, and this is not the way it should be. "sysctl dev" doesn't provide that information either. In this example, there are actually four devices on irq18: ohci2, ohci3, ohci4, vgapci0. About half of the machines I have access to exhibit that problem. Disclaimer: I'm not familiar with FreeBSD's interrupt code, so my opinion should be regarded as a "user's wish for enhancement", not as a developer's vote. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "The scanf() function is a large and complex beast that often does something almost but not quite entirely unlike what you desired." -- Chris Torek From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 08:52:27 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E82106568D; Wed, 14 Oct 2009 08:52:27 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1FF0F8FC0C; Wed, 14 Oct 2009 08:52:27 +0000 (UTC) Received: from outgoing.leidinger.net (pD9E2D96D.dip.t-dialin.net [217.226.217.109]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 009CF84450D; Wed, 14 Oct 2009 10:36:46 +0200 (CEST) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 3C97120DA5A; Wed, 14 Oct 2009 10:36:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1255509402; bh=xMG69Km+TL+FIFArJ78GLGQ1ksKtjflSahrEh2hyELI=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=UJCKX3GvsTcFjR58+f7HWwPZElzEzt4AUgCByc3aX5l3r+7+Psgv1qxs1/Sgws1lR 9x6lIBv/gbZ6JtuallW8dPCVvS2kooSczrGr10KAFHDHEE5hT/ymI/upFkJ4WfKW2u Tdotm3QmlYRu/IyzmAMsnKCKEwhF//MsMlen4yhyvqpx/1MnUb9vwTCJCfuYq2I7Nc Jsr7KwnlAAUWA9+pL8HMqbdhjT3g3rlIf1Bi8iHDVudyDebMkmKksku33Z6YM4SjVK ZOTn68VTRsReQnSn5YhksuRiCK/EGB6CF6sZ8vTHWaLIdSS00cKGLuOtypVHiSfWxP LD/+uJ2+qLMQA== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n9E8afG2025787; Wed, 14 Oct 2009 10:36:41 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 14 Oct 2009 10:36:40 +0200 Message-ID: <20091014103640.1364764w7rhf3e8s@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Wed, 14 Oct 2009 10:36:40 +0200 From: Alexander Leidinger To: Oliver Fromme References: <200910140811.n9E8BvKk063958@lurza.secnetix.de> In-Reply-To: <200910140811.n9E8BvKk063958@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.5) / FreeBSD-8.0 X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 009CF84450D.685B7 X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1.363, required 6, autolearn=disabled, ALL_TRUSTED -1.44, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, TW_JH 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1256114209.85182@dVsABQGLGz7HcwlprJMn3w X-EBL-Spam-Status: No Cc: mav@FreeBSD.ORG, jhb@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: improvement wishes (was: Re: Interrupt Descriptions) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 08:52:27 -0000 Quoting Oliver Fromme (from Wed, 14 Oct 2009 10:11:57 +0200 (CEST)): > Alexander Motin wrote: > > Just some 50 cents on topic: it would be nice if `vmstat -i` was able to > > show all (more then 2) consumers of shared interrupt instead of "cbb0 > > wpi0+". I haven't looked who actually limit this and why, so it's just a > > wish. > > Here's a whole-hearted "me too". > I also often have output like this from vmstat: > > irq18: ohci2 ohci+ > > It doesn't even display the number of the second ohci > device on irq18. So I always have to grep through > /var/run/dmegs.boot to find out the real list of > devices, which is annoying, and this is not the way > it should be. "sysctl dev" doesn't provide that > information either. > > In this example, there are actually four devices on > irq18: ohci2, ohci3, ohci4, vgapci0. To all those people with wishes which improve parts of FreeBSD. We have something where you can express your wishes much much better (an on topic) than here in this thread (where jhb is talking about something orthogonal). This other place I talk about is http://www.FreeBSD.org/projects/ideas/ or http://wiki.FreeBSD.org/. Both places are open for modification to everyone. Expressing your wishes there allows a fairy or genie to have a look at them. Bye, Alexander. -- Old age is too high a price to pay for maturity. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 08:54:50 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E06D106568B; Wed, 14 Oct 2009 08:54:50 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 888768FC18; Wed, 14 Oct 2009 08:54:49 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 22so221295fge.13 for ; Wed, 14 Oct 2009 01:54:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=lHAjmmjsua02kzJFa8/s5EeF3HoFaw7F5rZjvrt2hBg=; b=xYwkFah0LREND4FruTTi+9dMgb8bgf4NzqIryQuUQK45yV/dBgGFePoiO/+znKKu9F kfcHhXqwCFeMqWe1qgWVKdBXk7s8xDfh0+Ge5Y7Qsen54HjmPCohxYvzNf89+oC1PBP5 gW+qZa9FfloyasFl8frxzZrzDb7YHBt09P8RU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=pv7iLizXuVEiVfjQHgi3I7rRh2p8flKug16LEKm3SVj7UG/qB+czq+nDFymP2akg4L Gux0UqZM8xrX2J14UG5rkKI+zliGftAoq02c2kSGZzmQ2SFnfaqlKSgusV1d+ladZz8p EyatTSWKP6QVWBxbz/HR00mk0T2aYHZTLe+lA= Received: by 10.103.76.29 with SMTP id d29mr3619198mul.50.1255510488236; Wed, 14 Oct 2009 01:54:48 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 23sm1903762mun.3.2009.10.14.01.54.46 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Oct 2009 01:54:47 -0700 (PDT) Sender: Alexander Motin Message-ID: <4AD591D4.1090806@FreeBSD.org> Date: Wed, 14 Oct 2009 11:54:44 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Alexander Leidinger References: <200910140811.n9E8BvKk063958@lurza.secnetix.de> <20091014103640.1364764w7rhf3e8s@webmail.leidinger.net> In-Reply-To: <20091014103640.1364764w7rhf3e8s@webmail.leidinger.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Oliver Fromme , jhb@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: improvement wishes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 08:54:50 -0000 Alexander Leidinger wrote: > To all those people with wishes which improve parts of FreeBSD. We have > something where you can express your wishes much much better (an on > topic) than here in this thread (where jhb is talking about something > orthogonal). This other place I talk about is > http://www.FreeBSD.org/projects/ideas/ or http://wiki.FreeBSD.org/. Both > places are open for modification to everyone. Expressing your wishes > there allows a fairy or genie to have a look at them. The most efficient place to hunt right genie is near lamp where he lives. ;) Ideas page is cool for large projects, but This I hope should be easier to fix then publish somewhere for next few years. This topic is not completely orthogonal, as adding more information to the interrupt consumer name may result (hypothetically) that we won't see even second consumer of shared IRQ, instead of third. -- Alexander Motin From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 11:31:44 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B429C106568B; Wed, 14 Oct 2009 11:31:44 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from mail.ebusiness-leidinger.de (mail.ebusiness-leidinger.de [217.11.53.44]) by mx1.freebsd.org (Postfix) with ESMTP id 411FC8FC1A; Wed, 14 Oct 2009 11:31:44 +0000 (UTC) Received: from outgoing.leidinger.net (pD9E2D96D.dip.t-dialin.net [217.226.217.109]) by mail.ebusiness-leidinger.de (Postfix) with ESMTPSA id 8513284450C; Wed, 14 Oct 2009 13:31:36 +0200 (CEST) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 6001920DA09; Wed, 14 Oct 2009 13:31:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1255519893; bh=yq7vSgEz9WkjWemjQEz5n/alAIQ8S4yEofmlE60DwpY=; h=Message-ID:Date:From:To:Cc:Subject:References:In-Reply-To: MIME-Version:Content-Type:Content-Transfer-Encoding; b=pVJyDbedZVaYl9uGLlzbQHYUzLFl/B7vMzUWE6Bj/0hzihe0yKc2edYvefyyGK112 Vourqms6FjOuYXphf2cIcmESc5RIl1jkuhMjdbydXxv2BnaucGx1FfO3LcawsO7gBD OFsUoIAKOEt8LafeLZiyV43rpKpyfykHddwBxLgTCdObyeTUWvyKcdVuCe4twjYxA6 x2C8rjpJ4xb96j/pf5aQJv3LPtVJx0A3jPqsuM7VsKOUElKrPDy3NhIRLhrx7RYSMc CjN/vcsKIxt8f3d/q7ZSk7mEXvRFj8JzeJjzQJUOeEKG74psw2DCgLlwVL7h7EE9Zb 9Ost4chojHkzg== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n9EBVXQJ057211; Wed, 14 Oct 2009 13:31:33 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 14 Oct 2009 13:31:32 +0200 Message-ID: <20091014133132.63685a7ifac7jecc@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Wed, 14 Oct 2009 13:31:32 +0200 From: Alexander Leidinger To: Alexander Motin References: <200910140811.n9E8BvKk063958@lurza.secnetix.de> <20091014103640.1364764w7rhf3e8s@webmail.leidinger.net> <4AD591D4.1090806@FreeBSD.org> In-Reply-To: <4AD591D4.1090806@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.5) / FreeBSD-8.0 X-EBL-MailScanner-Information: Please contact the ISP for more information X-EBL-MailScanner-ID: 8513284450C.AFD7B X-EBL-MailScanner: Found to be clean X-EBL-MailScanner-SpamCheck: not spam, spamhaus-ZEN, SpamAssassin (not cached, score=-1.363, required 6, autolearn=disabled, ALL_TRUSTED -1.44, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, TW_JH 0.08) X-EBL-MailScanner-From: alexander@leidinger.net X-EBL-MailScanner-Watermark: 1256124698.69902@ePeynvXO494tg1rFWOLTAg X-EBL-Spam-Status: No Cc: Oliver Fromme , jhb@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: improvement wishes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 11:31:44 -0000 Quoting Alexander Motin (from Wed, 14 Oct 2009 11:54:44 +0300): > Alexander Leidinger wrote: >> To all those people with wishes which improve parts of FreeBSD. We have >> something where you can express your wishes much much better (an on >> topic) than here in this thread (where jhb is talking about something >> orthogonal). This other place I talk about is >> http://www.FreeBSD.org/projects/ideas/ or http://wiki.FreeBSD.org/. Both >> places are open for modification to everyone. Expressing your wishes >> there allows a fairy or genie to have a look at them. > > The most efficient place to hunt right genie is near lamp where he > lives. ;) Ideas page is cool for large projects, but This I hope should > be easier to fix then publish somewhere for next few years. Even small projects should be put online, that's better than to forget about it at all. The idea page is not only for the GSoC, but also for things which could serve as an entry point to FreeBSD-src-knowledge. > This topic is not completely orthogonal, as adding more information to > the interrupt consumer name may result (hypothetically) that we won't > see even second consumer of shared IRQ, instead of third. Let's say it differently: jhb wants to handle it orthogonal. :) Bye, Alexander. -- Professor: Oh, dear. She's stuck in an infinite loop and he's an idiot. Well, that's love for you. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 15:00:46 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A19C1065676; Wed, 14 Oct 2009 15:00:46 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4594A8FC15; Wed, 14 Oct 2009 15:00:46 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id D119146B1A; Wed, 14 Oct 2009 11:00:45 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id DC0568A01D; Wed, 14 Oct 2009 11:00:44 -0400 (EDT) From: John Baldwin To: Alexander Motin Date: Wed, 14 Oct 2009 07:57:58 -0400 User-Agent: KMail/1.9.7 References: <200909301732.20589.jhb@freebsd.org> <1255483383.00172964.1255470604@10.7.7.3> <4AD57B2C.8070606@FreeBSD.org> In-Reply-To: <4AD57B2C.8070606@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910140757.58887.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 14 Oct 2009 11:00:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-arch@freebsd.org Subject: Re: Interrupt Descriptions X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 15:00:46 -0000 On Wednesday 14 October 2009 3:18:04 am Alexander Motin wrote: > John Baldwin wrote: > > On Wednesday 30 September 2009 5:32:20 pm John Baldwin wrote: > >> A few folks have asked recently for the ability to add descriptive strings > > to > >> registered interrupt handlers. This is especially true since the advent of > >> MSI with multiple interrupts per device. I hacked up a prototype today that > >> adds a new 'bus_describe_intr()' that takes the IRQ resource, the void * > >> cookie returned by bus_setup_intr() and var args description and appends > > that > >> to the interrupt name in the thread and vmstat -i info. The current patch > >> only has the MI bits and the MD bits for amd64 as well as a sample change to > >> the igb(4) driver. > >> > >> The patch is at http://www.FreeBSD.org/~jhb/patches/intr_describe.patch. > >> > >> An example from this patch is: > >> > >>> vmstat -i > >> interrupt total rate > >> irq1: atkbd0 8 0 > >> irq4: uart0 751 5 > >> irq6: fdc0 6 0 > >> irq14: ata0 36 0 > >> irq20: uhci0 20 0 > >> irq23: uhci3 ehci0 2 0 > >> irq28: mpt0 1661 11 > >> irq256: igb0:tx 0 880 6 > >> irq257: igb0:rx 0 1098 7 > >> irq258: igb0:link 3 0 > >> irq259: igb1:tx 0 1 0 > >> irq260: igb1:rx 0 134 0 > >> irq261: igb1:link 3 0 > > > > Do folks feel that the issues with the intrnames and intrcnt API warrant > > delaying this work, or do folks have any objections to the proposed > > bus_describe_intr() API? Personally I think that intrnames and intrcnt are > > certainly broken, but that they have been broken for quite a while and that > > these changes do not make them more broken than they currently are. Also, I > > think that any fixes to intrcnt/intrnames would be orthogonal to > > bus_describe_intr(). > > Just some 50 cents on topic: it would be nice if `vmstat -i` was able to > show all (more then 2) consumers of shared interrupt instead of "cbb0 > wpi0+". I haven't looked who actually limit this and why, so it's just a > wish. At the moment the limit comes from stuffing the name into a p_comm[] (or in 8+ td_name[]) array which is limited to MAXCOMLEN in length. We also reuse that same name for the interrupt name in vmstat -i. Note that in 4.x before ithreads if you had a shared interrupt the vmstat -i output just said "mux" (check vmstat -i on ref4 for irq2) and did not tell you any of the devices at all, so a partial list is at least better than no list. We could generate a separate interrupt name for vmstat -i vs the ithread name, it's just a matter of space. We might do this if we move away from having static ithreads (i.e. having a pool of ithreads that are a specialized taskqueue that execute interrupt events). In that case the name would no longer be used for threads at all, so it could just be made longer, or possibly dynamically allocated. -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Wed Oct 14 15:00:47 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1E1A106568D; Wed, 14 Oct 2009 15:00:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8143A8FC16; Wed, 14 Oct 2009 15:00:47 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 3135846B2D; Wed, 14 Oct 2009 11:00:47 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 213798A01F; Wed, 14 Oct 2009 11:00:46 -0400 (EDT) From: John Baldwin To: Alexander Motin Date: Wed, 14 Oct 2009 08:08:57 -0400 User-Agent: KMail/1.9.7 References: <200910140811.n9E8BvKk063958@lurza.secnetix.de> <20091014103640.1364764w7rhf3e8s@webmail.leidinger.net> <4AD591D4.1090806@FreeBSD.org> In-Reply-To: <4AD591D4.1090806@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910140808.58205.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 14 Oct 2009 11:00:46 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Alexander Leidinger , Oliver Fromme , freebsd-arch@freebsd.org Subject: Re: improvement wishes X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 15:00:47 -0000 On Wednesday 14 October 2009 4:54:44 am Alexander Motin wrote: > Alexander Leidinger wrote: > > To all those people with wishes which improve parts of FreeBSD. We have > > something where you can express your wishes much much better (an on > > topic) than here in this thread (where jhb is talking about something > > orthogonal). This other place I talk about is > > http://www.FreeBSD.org/projects/ideas/ or http://wiki.FreeBSD.org/. Both > > places are open for modification to everyone. Expressing your wishes > > there allows a fairy or genie to have a look at them. > > The most efficient place to hunt right genie is near lamp where he > lives. ;) Ideas page is cool for large projects, but This I hope should > be easier to fix then publish somewhere for next few years. > > This topic is not completely orthogonal, as adding more information to > the interrupt consumer name may result (hypothetically) that we won't > see even second consumer of shared IRQ, instead of third. The reason why I am not worried about descriptions making the current situation worse is that descriptions are intended to be used for devices that have multiple interrupts. For devices with a single interrupt, the device name alone is a sufficiently unique label for the interrupt handler, but for devices with multiple interrupts having 3 "igb0" interrupts (for example) can be very ambiguous. Like so: irq256: igb0 641924 0 irq257: igb0 21245021 12 irq258: igb0 3 0 irq259: igb1 1160790 0 irq260: igb1 7595639 4 irq261: igb1 2 0 It would be handy to not have to refer to the source code of the driver to see what order it assigns interrupt handlers to figure out what is different about IRQs 256 vs 257 vs 258 for igb0. The only way devices can currently have multiple devices per interrupt is by using PCI MSI/MSI-X interrupts, and the current implementations of MSI ensure that MSI interrupts are never shared, so in practice you will not run into problems with descriptions causing loss of detail in existing interrupt stats. -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Thu Oct 15 12:01:18 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDF86106566C for ; Thu, 15 Oct 2009 12:01:18 +0000 (UTC) (envelope-from asientrade@freenet.de) Received: from mout6.freenet.de (mout6.freenet.de [IPv6:2001:748:100:40::2:8]) by mx1.freebsd.org (Postfix) with ESMTP id 073578FC2F for ; Thu, 15 Oct 2009 12:01:18 +0000 (UTC) Received: from [195.4.92.19] (helo=9.mx.freenet.de) by mout6.freenet.de with esmtpa (ID asientrade@freenet.de) (port 25) (Exim 4.69 #92) id 1MyP1B-0002ro-Ee for arch@freebsd.org; Thu, 15 Oct 2009 14:01:17 +0200 Received: from p5b12da1b.dip.t-dialin.net ([91.18.218.27]:55944 helo=daniel-PC) by 9.mx.freenet.de with esmtpa (ID asientrade@freenet.de) (port 587) (Exim 4.69 #94) id 1MyP0z-0005dz-AQ for arch@freebsd.org; Thu, 15 Oct 2009 14:01:17 +0200 From: "daniel" To: arch@freebsd.org Content-Type: multipart/related; boundary="----=_NextPart_766_F636_E7973656.97579622" MIME-Version: 1.0 Date: Thu, 15 Oct 2009 14:01:32 +0200 Message-Id: <2009101514012729CF1EF7EF$AD4939E28F@DANIELPC> Status: N X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Twitter-endlich Geldverdienen-kostenlos und sofort startklar X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bitteinfo1@freenet.de List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 12:01:18 -0000 This is a multi-part message in MIME format ------=_NextPart_766_F636_E7973656.97579622 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =A0Offers stand below as an English available Hallo- =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 verdiene endlich Geld durc= h Twitterwenn ein Twitter Account vorhanden sein sollte dann gehts sofort = los mit Verdienen.sollte keine Account vorhanden sein dann einfach alles kostenlos erstellen und verdienen.=A0mit besten Empfehlungen eure Danielleichter kann man sein =B4Geld nicht verdienen- alles kostenlos we= nn sie einen Twitteraccount haben.Also schnell handel-bei weiterem Interess= e und lust an gratis produkten einfach kurz anmelden-oder abmelden-- danke=A0=A0Anmelden=A0=A0=A0=A0=A0=A0 =A0Abmelden=A024 Std. Blitzangebot= =A0nur begrenzt f=FCr=A024 Stunden aktiv danach ausverkauft--- http://www.affiliateverkaufen.de/blitzangebot.html=A0=A0=A0=A0 10,-?(The= Logo Creator hilft beim Erstellen qualitativ hochwertiger Logos. Ganz nach de= m Motto "Your Logo is your business" gestaltet der Nutzer mit diesem Progr= amm Blickf=E4nger f=FCr Webseiten)=A0(=DCbersetzen Sie ganz einfach und mit = wenigen Klicks Texte oder sogar komplette Webseiten in 31 Sprachen. )nur 28,-?=A0= oder Aktionspreis 30,-?=A0=A0 f=FCr Logocreator v5 und PDF-Converter 6.0 dt.=A0= Oder m=F6chten sie lieber effektiv heute noch Geld verdienen und Zahlungen we= nn m=F6glich sofort erwirtschaften-?? dann mit diesem angebot was f=FCr mich selbstbehauptet das beste =FCberh= aupt war und ist--Geld durch Emails verdienen-aber keine centbetr=E4ge sonder= n sofort 10-20,-? sofort-zahlung innerhalb weniger minuten, ich habe zur zeit zwischen 5 und 20 Kunden pro tag (weltweit) bei einem verdienst pro emai= l von ca. 15,-? und ich betreibe keinerlei werbung oder verkaufe durchs telefon nein die= Kunden kommen zu mir und ich verdiene sehr gut-aber lesen sie selbst wen= n ihr interesse noch vorhanden ist weiter im Angebot 2.erfolgreiches Hande= ln w=FCnsche ich auf diesem Wege-bei weiteren Interessen k=F6nnen sie sichwiederholt eintragen um weitere Angebote und Gratis Geschenke zu erhalten........................(oder Abmelden).... Anmelden=A0=A0=A0=A0= Abmelden =A0Hello- finally earn money by Twitterthen immediately feels wrong with= earning if a Twitter account should be available. no-one should account = be available simply then everything free of charge make and earn. with bes= t recommendations yours Danielone can more easily money not earning everything be ' free if they have a Twitteraccount. -therefore act fast = simply registering or cancelling at broader interest and desire at free = products briefly, thank youBookingCancelling24 hour lightning supply=A0s= old off according to that actively for 24 hours only restrictedly - http://www.affiliateverkaufen.de/blitzangebot.html 10. ? (A The logo Creator helps to make high-quality logos. According to the motto "Your l= ogo is your business" the user completely forms with this programme eye-catc= her for web pages.) =A0 (Translate texts or even complete web pages for onl= y simply and a few clicks into 31 languages.) only 28. ? or special-offer= price 30. ? for Logocreator v5 and PDF-Converter of 6.0 dt. -or they wo= uld rather, today, still earn money effectively and immediately gain payment= s if possible? with this supply did but no cent amounts what was self claimed for me th= e best at all and is? I have 10-20,- ? immediately payment within less minutes, between 5 and = 20 customers per day (worldwide) at an income per e-mail from approx. 15. ?= at the moment by the telephone the customers no come to me and I earn very well and I = operate no advertising or sell but read them even if their interest is still further existing in the supply 2. Angebot 2.I wish on this at broa= der interests be able to do them himself a successful action waystyping repeated ........................ in to receive further offers and free = presents. (or cancel ) ..... Booking=A0 Cancelling=A0=A0=A0=A0 ------=_NextPart_766_F636_E7973656.97579622-- From owner-freebsd-arch@FreeBSD.ORG Thu Oct 15 13:40:16 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB530106566C for ; Thu, 15 Oct 2009 13:40:16 +0000 (UTC) (envelope-from asientrade@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id D647C8FC08 for ; Thu, 15 Oct 2009 13:40:15 +0000 (UTC) Received: from [195.4.92.12] (helo=2.mx.freenet.de) by mout0.freenet.de with esmtpa (ID asientrade@freenet.de) (port 25) (Exim 4.69 #92) id 1MyQYx-0006Et-9N for freebsd-arch@freebsd.org; Thu, 15 Oct 2009 15:40:15 +0200 Received: from p5b12da1b.dip.t-dialin.net ([91.18.218.27]:58186 helo=daniel-PC) by 2.mx.freenet.de with esmtpa (ID asientrade@freenet.de) (port 587) (Exim 4.69 #94) id 1MyQYo-0002n4-68 for freebsd-arch@freebsd.org; Thu, 15 Oct 2009 15:40:15 +0200 From: "daniel" To: freebsd-arch@freebsd.org Content-Type: multipart/related; boundary="----=_NextPart_766_F636_E7973656.97579622" MIME-Version: 1.0 Date: Thu, 15 Oct 2009 15:40:33 +0200 Message-Id: <2009101515403195FE7B7318$6480CC20E4@DANIELPC> Status: N X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Twitter-endlich Geldverdienen-kostenlos und sofort startklar X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bitteinfo1@freenet.de List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 13:40:16 -0000 This is a multi-part message in MIME format ------=_NextPart_766_F636_E7973656.97579622 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =A0Offers stand below as an English available Hallo- =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 verdiene endlich Geld durc= h Twitterwenn ein Twitter Account vorhanden sein sollte dann gehts sofort = los mit Verdienen.sollte keine Account vorhanden sein dann einfach alles kostenlos erstellen und verdienen.=A0mit besten Empfehlungen eure Danielleichter kann man sein =B4Geld nicht verdienen- alles kostenlos we= nn sie einen Twitteraccount haben.Also schnell handel-bei weiterem Interess= e und lust an gratis produkten einfach kurz anmelden-oder abmelden-- danke=A0=A0Anmelden=A0=A0=A0=A0=A0=A0 =A0Abmelden=A024 Std. Blitzangebot= =A0nur begrenzt f=FCr=A024 Stunden aktiv danach ausverkauft--- http://www.affiliateverkaufen.de/blitzangebot.html=A0=A0=A0=A0 10,-?(The= Logo Creator hilft beim Erstellen qualitativ hochwertiger Logos. Ganz nach de= m Motto "Your Logo is your business" gestaltet der Nutzer mit diesem Progr= amm Blickf=E4nger f=FCr Webseiten)=A0(=DCbersetzen Sie ganz einfach und mit = wenigen Klicks Texte oder sogar komplette Webseiten in 31 Sprachen. )nur 28,-?=A0= oder Aktionspreis 30,-?=A0=A0 f=FCr Logocreator v5 und PDF-Converter 6.0 dt.=A0= Oder m=F6chten sie lieber effektiv heute noch Geld verdienen und Zahlungen we= nn m=F6glich sofort erwirtschaften-?? dann mit diesem angebot was f=FCr mich selbstbehauptet das beste =FCberh= aupt war und ist--Geld durch Emails verdienen-aber keine centbetr=E4ge sonder= n sofort 10-20,-? sofort-zahlung innerhalb weniger minuten, ich habe zur zeit zwischen 5 und 20 Kunden pro tag (weltweit) bei einem verdienst pro emai= l von ca. 15,-? und ich betreibe keinerlei werbung oder verkaufe durchs telefon nein die= Kunden kommen zu mir und ich verdiene sehr gut-aber lesen sie selbst wen= n ihr interesse noch vorhanden ist weiter im Angebot 2.erfolgreiches Hande= ln w=FCnsche ich auf diesem Wege-bei weiteren Interessen k=F6nnen sie sichwiederholt eintragen um weitere Angebote und Gratis Geschenke zu erhalten........................(oder Abmelden).... Anmelden=A0=A0=A0=A0= Abmelden =A0Hello- finally earn money by Twitterthen immediately feels wrong with= earning if a Twitter account should be available. no-one should account = be available simply then everything free of charge make and earn. with bes= t recommendations yours Danielone can more easily money not earning everything be ' free if they have a Twitteraccount. -therefore act fast = simply registering or cancelling at broader interest and desire at free = products briefly, thank youBookingCancelling24 hour lightning supply=A0s= old off according to that actively for 24 hours only restrictedly - http://www.affiliateverkaufen.de/blitzangebot.html 10. ? (A The logo Creator helps to make high-quality logos. According to the motto "Your l= ogo is your business" the user completely forms with this programme eye-catc= her for web pages.) =A0 (Translate texts or even complete web pages for onl= y simply and a few clicks into 31 languages.) only 28. ? or special-offer= price 30. ? for Logocreator v5 and PDF-Converter of 6.0 dt. -or they wo= uld rather, today, still earn money effectively and immediately gain payment= s if possible? with this supply did but no cent amounts what was self claimed for me th= e best at all and is? I have 10-20,- ? immediately payment within less minutes, between 5 and = 20 customers per day (worldwide) at an income per e-mail from approx. 15. ?= at the moment by the telephone the customers no come to me and I earn very well and I = operate no advertising or sell but read them even if their interest is still further existing in the supply 2. Angebot 2.I wish on this at broa= der interests be able to do them himself a successful action waystyping repeated ........................ in to receive further offers and free = presents. (or cancel ) ..... Booking=A0 Cancelling=A0=A0=A0=A0 ------=_NextPart_766_F636_E7973656.97579622-- From owner-freebsd-arch@FreeBSD.ORG Thu Oct 15 19:52:41 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 826AC106566C; Thu, 15 Oct 2009 19:52:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 24C9A8FC1F; Thu, 15 Oct 2009 19:52:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n9FJjIe1043543; Thu, 15 Oct 2009 13:45:18 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 15 Oct 2009 13:45:32 -0600 (MDT) Message-Id: <20091015.134532.-1110324186.imp@bsdimp.com> To: jkim@freebsd.org From: "M. Warner Losh" In-Reply-To: <200910151431.53236.jkim@FreeBSD.org> References: <20091015.085910.-520412456.imp@bsdimp.com> <200910151118.50619.jhb@freebsd.org> <200910151431.53236.jkim@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, xcllnt@mac.com Subject: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 19:52:41 -0000 [[ redirected to arch@ ]] In message: <200910151431.53236.jkim@FreeBSD.org> Jung-uk Kim writes: : This is actually very interesting discussion for me because one of my : pet projects is extending x86bios to support non-PC architectures. : If anyone is interested, the current source tarball is here: : : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 : : Especially, please see the code around #ifdef X86BIOS_COMPAT_ARCH. : Basically, mapping I/O ports and orm(4) is missing. We don't have to : implement I/O ports but orm(4) vs. bus_space(9) is critical to make : it a reality. Please consider it as a real practical example for : orm, not just a blackhole driver. :-) I thought that most video cards had I/O ports as well as video RAM that needed to be mapped... Am I crazy? I'm looking at the code and have a few questions. It looks like you are allocating memory from 0x1000 to 0xa0000 with a contig malloc, and then redirecting the emulator's read/write into that array. But I don't see where the memory reads for the so-called ISA ROM hole are going. I was looking for that hoping I could find them so I could comment on them... orm uses bus_space today to do its read/write of the memory. I'd imagine that if you wanted to touch actual hardware, then you'd need to have drivers and/or the emulator use the same path to accomplish this. While in theory one could have multiple ISA busses in a system, as a practical matter nobody does this. Even when you have weird expansion busses on laptop docking stations, you'd have them all mapped into one space. This means we can likely make some simplifying assumptions that there is a single ISA bus on the system. I don't know if we have to make that assumption, but it is something to keep in the back of our heads. This suggests that the emulation device would have to attach somehow to the ISA bus to make sure that the right translations (wherever they happen) can happen. But there's a catch... The readw/readb macros in the atkbd.c driver likely need to change to bus space macros of some kind to make this work. I'm unsure how, exactly, to make that happen since these addresses aren't for anything on the actual ISA bus, but rather are for data that's contained in the contigmalloc'd area. They aren't really ISA bus addresses, yet they are expected to be there by the drivers. bus_space suggests itself for this as well, but it isn't at all clear how that might be accomplished because ES could point anywhere in the first MB of RAM (since 16-bit operations are limited to 1MB with segments, right?) This is a very interesting project... Is the goal to emulate the BIOS or execute the BIOS that might be loaded on the expansion cards in these weird environments. I'm guessing the former, but you never know.. Warner From owner-freebsd-arch@FreeBSD.ORG Thu Oct 15 20:37:17 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CE1B1065679; Thu, 15 Oct 2009 20:37:17 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout027.mac.com (asmtpout027.mac.com [17.148.16.102]) by mx1.freebsd.org (Postfix) with ESMTP id 473458FC08; Thu, 15 Oct 2009 20:37:17 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii; format=flowed; delsp=yes Received: from macbook-pro.lan.xcllnt.net (mail.xcllnt.net [75.101.29.67]) by asmtp027.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KRK00B5KP9Q0Z40@asmtp027.mac.com>; Thu, 15 Oct 2009 13:37:05 -0700 (PDT) From: Marcel Moolenaar In-reply-to: <20091015.134532.-1110324186.imp@bsdimp.com> Date: Thu, 15 Oct 2009 13:37:02 -0700 Message-id: <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> References: <20091015.085910.-520412456.imp@bsdimp.com> <200910151118.50619.jhb@freebsd.org> <200910151431.53236.jkim@FreeBSD.org> <20091015.134532.-1110324186.imp@bsdimp.com> To: "M. Warner Losh" X-Mailer: Apple Mail (2.1076) Cc: arch@freebsd.org, jkim@freebsd.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 20:37:17 -0000 On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > [[ redirected to arch@ ]] > > In message: <200910151431.53236.jkim@FreeBSD.org> > Jung-uk Kim writes: > > : This is actually very interesting discussion for me because one of > my > : pet projects is extending x86bios to support non-PC architectures. > : If anyone is interested, the current source tarball is here: > : > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > : > : Especially, please see the code around #ifdef X86BIOS_COMPAT_ARCH. > : Basically, mapping I/O ports and orm(4) is missing. We don't have > to > : implement I/O ports but orm(4) vs. bus_space(9) is critical to make > : it a reality. Please consider it as a real practical example for > : orm, not just a blackhole driver. :-) > > I thought that most video cards had I/O ports as well as video RAM > that needed to be mapped... Am I crazy? It depends on the platform. On an Itanium machine I have the VGA frame buffer is at physical address 0xA0000-0xC0000. The only requirement is that you use non-cached I/O, otherwise you get a machine check. This can mean a non-identity mapping or not. It all depends... I/O ports don't exist and there's a memory region for generating I/O port accesses, but the translation is not linear, so you can't work with a single base and port offset to get this to work. See ia64_ioport_address() in sys/ia64/ia64/machdep.c -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-arch@FreeBSD.ORG Thu Oct 15 23:48:43 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 28D011065672; Thu, 15 Oct 2009 23:48:39 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "M. Warner Losh" Date: Thu, 15 Oct 2009 19:48:23 -0400 User-Agent: KMail/1.6.2 References: <20091015.085910.-520412456.imp@bsdimp.com> <200910151431.53236.jkim@FreeBSD.org> <20091015.134532.-1110324186.imp@bsdimp.com> In-Reply-To: <20091015.134532.-1110324186.imp@bsdimp.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910151948.31334.jkim@FreeBSD.org> Cc: arch@freebsd.org, xcllnt@mac.com Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 23:48:43 -0000 On Thursday 15 October 2009 03:45 pm, M. Warner Losh wrote: > [[ redirected to arch@ ]] > > In message: <200910151431.53236.jkim@FreeBSD.org> > Jung-uk Kim writes: > > > : This is actually very interesting discussion for me because one > : of my pet projects is extending x86bios to support non-PC > : architectures. If anyone is interested, the current source > : tarball is here: > : > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > : > : Especially, please see the code around #ifdef > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and orm(4) is > : missing. We don't have to implement I/O ports but orm(4) vs. > : bus_space(9) is critical to make it a reality. Please consider > : it as a real practical example for orm, not just a blackhole > : driver. :-) > > I thought that most video cards had I/O ports as well as video RAM > that needed to be mapped... Am I crazy? No, you are not. It's just a non-functional prototype for non-PC architectures. :-) > I'm looking at the code and have a few questions. > > It looks like you are allocating memory from 0x1000 to 0xa0000 with > a contig malloc, and then redirecting the emulator's read/write > into that array. But I don't see where the memory reads for the > so-called ISA ROM hole are going. I was looking for that hoping I > could find them so I could comment on them... You mean 15-16MB ISA hole, right? It's not implemented yet. Probably I should but I haven't seen any BIOS requiring the memory hole ATM. > orm uses bus_space today to do its read/write of the memory. I'd > imagine that if you wanted to touch actual hardware, then you'd > need to have drivers and/or the emulator use the same path to > accomplish this. Actually that's my goal but I wasn't sure whether it is ever usable on *non-PC* arches. Then, orm(4) debate caught my eyes. :-) > While in theory one could have multiple ISA busses in a system, as > a practical matter nobody does this. Even when you have weird > expansion busses on laptop docking stations, you'd have them all > mapped into one space. This means we can likely make some > simplifying assumptions that there is a single ISA bus on the > system. I don't know if we have to make that assumption, but it is > something to keep in the back of our heads. Thanks, I will keep that in mind. > This suggests that the emulation device would have to attach > somehow to the ISA bus to make sure that the right translations > (wherever they happen) can happen. But there's a catch... > > The readw/readb macros in the atkbd.c driver likely need to change > to bus space macros of some kind to make this work. I'm unsure > how, exactly, to make that happen since these addresses aren't for > anything on the actual ISA bus, but rather are for data that's > contained in the contigmalloc'd area. They aren't really ISA bus > addresses, yet they are expected to be there by the drivers. No, I have no intention to support BDA emulation, never. :-) Only IVT will be supported, e.g., vesa(4) calls POST on non-PC arches and it sets up the INT 10h vector. Subsequent INT 10h calls are naturally emulated. > bus_space suggests itself for this as well, but it isn't at all > clear how that might be accomplished because ES could point > anywhere in the first MB of RAM (since 16-bit operations are > limited to 1MB with segments, right?) Correct. > This is a very interesting project... Is the goal to emulate the > BIOS or execute the BIOS that might be loaded on the expansion > cards in these weird environments. I'm guessing the former, but > you never know.. Yes, it's the former, at least for now, e.g., using VBE calls on powerpc or sparc64. If my memory serves, NetBSD or OpenBSD can call video POST in ddb when display is corrupt, I think. Jung-uk Kim From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 17:46:17 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id E99F61065670; Fri, 16 Oct 2009 17:46:15 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-arch@FreeBSD.org Date: Fri, 16 Oct 2009 13:46:01 -0400 User-Agent: KMail/1.6.2 References: <20091015.085910.-520412456.imp@bsdimp.com> <20091015.134532.-1110324186.imp@bsdimp.com> <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> In-Reply-To: <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910161346.03066.jkim@FreeBSD.org> Cc: Marcel Moolenaar Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 17:46:17 -0000 On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > > [[ redirected to arch@ ]] > > > > In message: <200910151431.53236.jkim@FreeBSD.org> > > Jung-uk Kim writes: > > > > > > : This is actually very interesting discussion for me because one > > : of > > > > my > > > > : pet projects is extending x86bios to support non-PC > > : architectures. If anyone is interested, the current source > > : tarball is here: > > : > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > > : > > : Especially, please see the code around #ifdef > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and orm(4) is > > : missing. We don't have > > > > to > > > > : implement I/O ports but orm(4) vs. bus_space(9) is critical to > > : make it a reality. Please consider it as a real practical > > : example for orm, not just a blackhole driver. :-) > > > > I thought that most video cards had I/O ports as well as video > > RAM that needed to be mapped... Am I crazy? > > It depends on the platform. On an Itanium machine I have the > VGA frame buffer is at physical address 0xA0000-0xC0000. The address is the same, then. :-) > The only requirement is that you use non-cached I/O, otherwise > you get a machine check. This can mean a non-identity mapping > or not. It all depends... I couldn't find a way to manipulate memory attribute directly on ia64, i.e., mem_range_attr_{get,set}() and pmap_mapdev_attr() only exist on amd64 and i386. Does pmap_mapdev() set the attribute as UC? > I/O ports don't exist and there's a memory region for generating > I/O port accesses, but the translation is not linear, so you > can't work with a single base and port offset to get this to work. > See ia64_ioport_address() in sys/ia64/ia64/machdep.c It seems there are PC-compatible inline functions {in,out}[bwl] in sys/ia64/include/cpufunc.h. Will they work as I expect? Thanks, Jung-uk Kim From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 18:00:20 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 266ED1065679; Fri, 16 Oct 2009 18:00:19 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-arch@FreeBSD.org Date: Fri, 16 Oct 2009 13:59:58 -0400 User-Agent: KMail/1.6.2 References: <20091015.085910.-520412456.imp@bsdimp.com> <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> <200910161346.03066.jkim@FreeBSD.org> In-Reply-To: <200910161346.03066.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910161400.00564.jkim@FreeBSD.org> Cc: Marcel Moolenaar Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 18:00:20 -0000 On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > > > [[ redirected to arch@ ]] > > > > > > In message: <200910151431.53236.jkim@FreeBSD.org> > > > Jung-uk Kim writes: > > > > > > > > > : This is actually very interesting discussion for me because > > > : one of > > > > > > my > > > > > > : pet projects is extending x86bios to support non-PC > > > : architectures. If anyone is interested, the current source > > > : tarball is here: > > > : > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > > > : > > > : Especially, please see the code around #ifdef > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and orm(4) > > > : is missing. We don't have > > > > > > to > > > > > > : implement I/O ports but orm(4) vs. bus_space(9) is critical > > > : to make it a reality. Please consider it as a real practical > > > : example for orm, not just a blackhole driver. :-) > > > > > > I thought that most video cards had I/O ports as well as video > > > RAM that needed to be mapped... Am I crazy? > > > > It depends on the platform. On an Itanium machine I have the > > VGA frame buffer is at physical address 0xA0000-0xC0000. > > The address is the same, then. :-) > > > The only requirement is that you use non-cached I/O, otherwise > > you get a machine check. This can mean a non-identity mapping > > or not. It all depends... > > I couldn't find a way to manipulate memory attribute directly on > ia64, i.e., mem_range_attr_{get,set}() and pmap_mapdev_attr() only > exist on amd64 and i386. Does pmap_mapdev() set the attribute as > UC? It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If I read the source correctly, then it is gives UC mapped "view" of the physical address, right? If so, orm(4) can simply do pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). Am I right? Jung-uk Kim > > I/O ports don't exist and there's a memory region for generating > > I/O port accesses, but the translation is not linear, so you > > can't work with a single base and port offset to get this to > > work. See ia64_ioport_address() in sys/ia64/ia64/machdep.c > > It seems there are PC-compatible inline functions {in,out}[bwl] in > sys/ia64/include/cpufunc.h. Will they work as I expect? > > Thanks, > > Jung-uk Kim From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 18:27:47 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E5B1065672; Fri, 16 Oct 2009 18:27:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id C76578FC25; Fri, 16 Oct 2009 18:27:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n9GIPdm4055539; Fri, 16 Oct 2009 12:25:39 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 16 Oct 2009 12:25:39 -0600 (MDT) Message-Id: <20091016.122539.-1383511515.imp@bsdimp.com> To: jkim@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200910161400.00564.jkim@FreeBSD.org> References: <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> <200910161346.03066.jkim@FreeBSD.org> <200910161400.00564.jkim@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: xcllnt@mac.com, freebsd-arch@FreeBSD.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 18:27:47 -0000 In message: <200910161400.00564.jkim@FreeBSD.org> Jung-uk Kim writes: : On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: : > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: : > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: : > > > [[ redirected to arch@ ]] : > > > : > > > In message: <200910151431.53236.jkim@FreeBSD.org> : > > > Jung-uk Kim writes: : > > > : > > > : > > > : This is actually very interesting discussion for me because : > > > : one of : > > > : > > > my : > > > : > > > : pet projects is extending x86bios to support non-PC : > > > : architectures. If anyone is interested, the current source : > > > : tarball is here: : > > > : : > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 : > > > : : > > > : Especially, please see the code around #ifdef : > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and orm(4) : > > > : is missing. We don't have : > > > : > > > to : > > > : > > > : implement I/O ports but orm(4) vs. bus_space(9) is critical : > > > : to make it a reality. Please consider it as a real practical : > > > : example for orm, not just a blackhole driver. :-) : > > > : > > > I thought that most video cards had I/O ports as well as video : > > > RAM that needed to be mapped... Am I crazy? : > > : > > It depends on the platform. On an Itanium machine I have the : > > VGA frame buffer is at physical address 0xA0000-0xC0000. : > : > The address is the same, then. :-) : > : > > The only requirement is that you use non-cached I/O, otherwise : > > you get a machine check. This can mean a non-identity mapping : > > or not. It all depends... : > : > I couldn't find a way to manipulate memory attribute directly on : > ia64, i.e., mem_range_attr_{get,set}() and pmap_mapdev_attr() only : > exist on amd64 and i386. Does pmap_mapdev() set the attribute as : > UC? : : It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If I : read the source correctly, then it is gives UC mapped "view" of the : physical address, right? If so, orm(4) can simply do : pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). Am I : right? I don't think that's the right solution here. The pmap_mapdev stuff should happen when the resource is activated... Warner From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 18:36:24 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0836B106566B; Fri, 16 Oct 2009 18:36:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B755A8FC12; Fri, 16 Oct 2009 18:36:23 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4D0F646B2D; Fri, 16 Oct 2009 14:36:23 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 90C058A01D; Fri, 16 Oct 2009 14:36:22 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Date: Fri, 16 Oct 2009 14:19:07 -0400 User-Agent: KMail/1.9.7 References: <20091015.085910.-520412456.imp@bsdimp.com> <200910161346.03066.jkim@FreeBSD.org> <200910161400.00564.jkim@FreeBSD.org> In-Reply-To: <200910161400.00564.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910161419.08369.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 16 Oct 2009 14:36:22 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Marcel Moolenaar , Jung-uk Kim Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 18:36:24 -0000 On Friday 16 October 2009 1:59:58 pm Jung-uk Kim wrote: > On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: > > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: > > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > > > > [[ redirected to arch@ ]] > > > > > > > > In message: <200910151431.53236.jkim@FreeBSD.org> > > > > Jung-uk Kim writes: > > > > > > > > > > > > : This is actually very interesting discussion for me because > > > > : one of > > > > > > > > my > > > > > > > > : pet projects is extending x86bios to support non-PC > > > > : architectures. If anyone is interested, the current source > > > > : tarball is here: > > > > : > > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > > > > : > > > > : Especially, please see the code around #ifdef > > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and orm(4) > > > > : is missing. We don't have > > > > > > > > to > > > > > > > > : implement I/O ports but orm(4) vs. bus_space(9) is critical > > > > : to make it a reality. Please consider it as a real practical > > > > : example for orm, not just a blackhole driver. :-) > > > > > > > > I thought that most video cards had I/O ports as well as video > > > > RAM that needed to be mapped... Am I crazy? > > > > > > It depends on the platform. On an Itanium machine I have the > > > VGA frame buffer is at physical address 0xA0000-0xC0000. > > > > The address is the same, then. :-) > > > > > The only requirement is that you use non-cached I/O, otherwise > > > you get a machine check. This can mean a non-identity mapping > > > or not. It all depends... > > > > I couldn't find a way to manipulate memory attribute directly on > > ia64, i.e., mem_range_attr_{get,set}() and pmap_mapdev_attr() only > > exist on amd64 and i386. Does pmap_mapdev() set the attribute as > > UC? > > It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If I > read the source correctly, then it is gives UC mapped "view" of the > physical address, right? If so, orm(4) can simply do > pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). Am I > right? I think you need to back up a bit. Instead of having a bunch of MD code to provide ISA access for each arch, instead do what Warner suggests which is to create a psuedo ISA device that attaches to isa0 and acts as a proxy for ISA I/O. It can allocate ISA resources for both memory and I/O access and then use bus_space_*() accesses to perform actual I/O. This will be MI. The only problem I can see with this approach is if a BIOS call attempts to frob a resource that another ISA device already owns. There may be ways around that though. -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 19:04:18 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 673D71065679; Fri, 16 Oct 2009 19:04:18 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "M. Warner Losh" Date: Fri, 16 Oct 2009 15:04:07 -0400 User-Agent: KMail/1.6.2 References: <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> <200910161400.00564.jkim@FreeBSD.org> <20091016.122539.-1383511515.imp@bsdimp.com> In-Reply-To: <20091016.122539.-1383511515.imp@bsdimp.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910161504.09685.jkim@FreeBSD.org> Cc: xcllnt@mac.com, freebsd-arch@FreeBSD.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 19:04:18 -0000 On Friday 16 October 2009 02:25 pm, M. Warner Losh wrote: > In message: <200910161400.00564.jkim@FreeBSD.org> > > Jung-uk Kim writes: > : On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: > : > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: > : > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > : > > > [[ redirected to arch@ ]] > : > > > > : > > > In message: <200910151431.53236.jkim@FreeBSD.org> > : > > > Jung-uk Kim writes: > : > > > > : > > > > : > > > : This is actually very interesting discussion for me > : > > > : because one of > : > > > > : > > > my > : > > > > : > > > : pet projects is extending x86bios to support non-PC > : > > > : architectures. If anyone is interested, the current > : > > > : source tarball is here: > : > > > : > : > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > : > > > : > : > > > : Especially, please see the code around #ifdef > : > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and > : > > > : orm(4) is missing. We don't have > : > > > > : > > > to > : > > > > : > > > : implement I/O ports but orm(4) vs. bus_space(9) is > : > > > : critical to make it a reality. Please consider it as a > : > > > : real practical example for orm, not just a blackhole > : > > > : driver. :-) > : > > > > : > > > I thought that most video cards had I/O ports as well as > : > > > video RAM that needed to be mapped... Am I crazy? > : > > > : > > It depends on the platform. On an Itanium machine I have the > : > > VGA frame buffer is at physical address 0xA0000-0xC0000. > : > > : > The address is the same, then. :-) > : > > : > > The only requirement is that you use non-cached I/O, > : > > otherwise you get a machine check. This can mean a > : > > non-identity mapping or not. It all depends... > : > > : > I couldn't find a way to manipulate memory attribute directly > : > on ia64, i.e., mem_range_attr_{get,set}() and > : > pmap_mapdev_attr() only exist on amd64 and i386. Does > : > pmap_mapdev() set the attribute as UC? > : > : It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If > : I read the source correctly, then it is gives UC mapped "view" of > : the physical address, right? If so, orm(4) can simply do > : pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). > : Am I right? > > I don't think that's the right solution here. The pmap_mapdev > stuff should happen when the resource is activated... For that, I guess we need another resource flag, e.g., RF_DEVICE, maybe? Jung-uk Kim From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 19:17:46 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 83B221065696; Fri, 16 Oct 2009 19:17:46 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: John Baldwin Date: Fri, 16 Oct 2009 15:17:35 -0400 User-Agent: KMail/1.6.2 References: <20091015.085910.-520412456.imp@bsdimp.com> <200910161400.00564.jkim@FreeBSD.org> <200910161419.08369.jhb@freebsd.org> In-Reply-To: <200910161419.08369.jhb@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910161517.37518.jkim@FreeBSD.org> Cc: Marcel Moolenaar , freebsd-arch@freebsd.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 19:17:46 -0000 On Friday 16 October 2009 02:19 pm, John Baldwin wrote: > On Friday 16 October 2009 1:59:58 pm Jung-uk Kim wrote: > > On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: > > > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: > > > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: > > > > > [[ redirected to arch@ ]] > > > > > > > > > > In message: <200910151431.53236.jkim@FreeBSD.org> > > > > > Jung-uk Kim writes: > > > > > > > > > > > > > > > : This is actually very interesting discussion for me > > > > > : because one of > > > > > > > > > > my > > > > > > > > > > : pet projects is extending x86bios to support non-PC > > > > > : architectures. If anyone is interested, the current > > > > > : source tarball is here: > > > > > : > > > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 > > > > > : > > > > > : Especially, please see the code around #ifdef > > > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and > > > > > : orm(4) is missing. We don't have > > > > > > > > > > to > > > > > > > > > > : implement I/O ports but orm(4) vs. bus_space(9) is > > > > > : critical to make it a reality. Please consider it as a > > > > > : real practical example for orm, not just a blackhole > > > > > : driver. :-) > > > > > > > > > > I thought that most video cards had I/O ports as well as > > > > > video RAM that needed to be mapped... Am I crazy? > > > > > > > > It depends on the platform. On an Itanium machine I have the > > > > VGA frame buffer is at physical address 0xA0000-0xC0000. > > > > > > The address is the same, then. :-) > > > > > > > The only requirement is that you use non-cached I/O, > > > > otherwise you get a machine check. This can mean a > > > > non-identity mapping or not. It all depends... > > > > > > I couldn't find a way to manipulate memory attribute directly > > > on ia64, i.e., mem_range_attr_{get,set}() and > > > pmap_mapdev_attr() only exist on amd64 and i386. Does > > > pmap_mapdev() set the attribute as UC? > > > > It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If > > I read the source correctly, then it is gives UC mapped "view" of > > the physical address, right? If so, orm(4) can simply do > > pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). > > Am I right? > > I think you need to back up a bit. Instead of having a bunch of MD > code to provide ISA access for each arch, instead do what Warner > suggests which is to create a psuedo ISA device that attaches to > isa0 and acts as a proxy for ISA I/O. It can allocate ISA > resources for both memory and I/O access and then use bus_space_*() > accesses to perform actual I/O. This will be MI. The only problem > I can see with this approach is if a BIOS call attempts to frob a > resource that another ISA device already owns. There may be ways > around that though. That's very interesting idea and it may be very useful for paravirtualized environment, I guess. However, it's beyond my free time. :-( Just in case, I updated the source and uploaded it here: http://people.freebsd.org/~jkim/x86bios-20091016.tar.bz2 For the efficiency reasons, I'd like to keep the amd64/i386 code as is. Feel free to fill in the MI implementation if you want. Thanks, Jung-uk Kim From owner-freebsd-arch@FreeBSD.ORG Fri Oct 16 19:34:32 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CAB5106566C; Fri, 16 Oct 2009 19:34:32 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B3BA18FC1E; Fri, 16 Oct 2009 19:34:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n9GJPVga056100; Fri, 16 Oct 2009 13:25:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 16 Oct 2009 13:25:31 -0600 (MDT) Message-Id: <20091016.132531.377201063.imp@bsdimp.com> To: jkim@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200910161504.09685.jkim@FreeBSD.org> References: <200910161400.00564.jkim@FreeBSD.org> <20091016.122539.-1383511515.imp@bsdimp.com> <200910161504.09685.jkim@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: xcllnt@mac.com, freebsd-arch@FreeBSD.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 19:34:32 -0000 In message: <200910161504.09685.jkim@FreeBSD.org> Jung-uk Kim writes: : On Friday 16 October 2009 02:25 pm, M. Warner Losh wrote: : > In message: <200910161400.00564.jkim@FreeBSD.org> : > : > Jung-uk Kim writes: : > : On Friday 16 October 2009 01:46 pm, Jung-uk Kim wrote: : > : > On Thursday 15 October 2009 04:37 pm, Marcel Moolenaar wrote: : > : > > On Oct 15, 2009, at 12:45 PM, M. Warner Losh wrote: : > : > > > [[ redirected to arch@ ]] : > : > > > : > : > > > In message: <200910151431.53236.jkim@FreeBSD.org> : > : > > > Jung-uk Kim writes: : > : > > > : > : > > > : > : > > > : This is actually very interesting discussion for me : > : > > > : because one of : > : > > > : > : > > > my : > : > > > : > : > > > : pet projects is extending x86bios to support non-PC : > : > > > : architectures. If anyone is interested, the current : > : > > > : source tarball is here: : > : > > > : : > : > > > : http://people.freebsd.org/~jkim/x86bios-20091015.tar.bz2 : > : > > > : : > : > > > : Especially, please see the code around #ifdef : > : > > > : X86BIOS_COMPAT_ARCH. Basically, mapping I/O ports and : > : > > > : orm(4) is missing. We don't have : > : > > > : > : > > > to : > : > > > : > : > > > : implement I/O ports but orm(4) vs. bus_space(9) is : > : > > > : critical to make it a reality. Please consider it as a : > : > > > : real practical example for orm, not just a blackhole : > : > > > : driver. :-) : > : > > > : > : > > > I thought that most video cards had I/O ports as well as : > : > > > video RAM that needed to be mapped... Am I crazy? : > : > > : > : > > It depends on the platform. On an Itanium machine I have the : > : > > VGA frame buffer is at physical address 0xA0000-0xC0000. : > : > : > : > The address is the same, then. :-) : > : > : > : > > The only requirement is that you use non-cached I/O, : > : > > otherwise you get a machine check. This can mean a : > : > > non-identity mapping or not. It all depends... : > : > : > : > I couldn't find a way to manipulate memory attribute directly : > : > on ia64, i.e., mem_range_attr_{get,set}() and : > : > pmap_mapdev_attr() only exist on amd64 and i386. Does : > : > pmap_mapdev() set the attribute as UC? : > : : > : It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If : > : I read the source correctly, then it is gives UC mapped "view" of : > : the physical address, right? If so, orm(4) can simply do : > : pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). : > : Am I right? : > : > I don't think that's the right solution here. The pmap_mapdev : > stuff should happen when the resource is activated... : : For that, I guess we need another resource flag, e.g., RF_DEVICE, : maybe? No. The activate will be able to do this. If we need to, we can move the activate from MI to MD. Warner From owner-freebsd-arch@FreeBSD.ORG Sat Oct 17 05:09:37 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 481C4106566C for ; Sat, 17 Oct 2009 05:09:37 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout023.mac.com (asmtpout023.mac.com [17.148.16.98]) by mx1.freebsd.org (Postfix) with ESMTP id 33E688FC18 for ; Sat, 17 Oct 2009 05:09:37 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii; format=flowed Received: from macbook-pro.lan.xcllnt.net (mail.xcllnt.net [75.101.29.67]) by asmtp023.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KRN00CF84VUJC90@asmtp023.mac.com>; Fri, 16 Oct 2009 21:09:31 -0700 (PDT) From: Marcel Moolenaar In-reply-to: <200910161346.03066.jkim@FreeBSD.org> Date: Fri, 16 Oct 2009 21:09:30 -0700 Message-id: <7178B392-D211-41C3-80DC-97E90263B8B7@mac.com> References: <20091015.085910.-520412456.imp@bsdimp.com> <20091015.134532.-1110324186.imp@bsdimp.com> <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> <200910161346.03066.jkim@FreeBSD.org> To: Jung-uk Kim X-Mailer: Apple Mail (2.1076) Cc: freebsd-arch@FreeBSD.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 05:09:37 -0000 On Oct 16, 2009, at 10:46 AM, Jung-uk Kim wrote: >>> >>> I thought that most video cards had I/O ports as well as video >>> RAM that needed to be mapped... Am I crazy? >> >> It depends on the platform. On an Itanium machine I have the >> VGA frame buffer is at physical address 0xA0000-0xC0000. > > The address is the same, then. :-) On this one machine it happens to be the same. On another machine there's no addressable memory below 768TB (yes, terabyte), so as I said: it depends. >> The only requirement is that you use non-cached I/O, otherwise >> you get a machine check. This can mean a non-identity mapping >> or not. It all depends... > > I couldn't find a way to manipulate memory attribute directly on ia64, > i.e., mem_range_attr_{get,set}() and pmap_mapdev_attr() only exist on > amd64 and i386. Does pmap_mapdev() set the attribute as UC? New KPIs are typically only implemented for i386 and amd64. It's one of the many unnecessary difficulties one faces when trying to port or maintain a platform. > It seems there are PC-compatible inline functions {in,out}[bwl] in > sys/ia64/include/cpufunc.h. Will they work as I expect? Yes, but it's always been my intention to remove them. Don't base any implementation on the existence of these... FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-arch@FreeBSD.ORG Sat Oct 17 05:12:39 2009 Return-Path: Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A9FC1065692 for ; Sat, 17 Oct 2009 05:12:39 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout027.mac.com (asmtpout027.mac.com [17.148.16.102]) by mx1.freebsd.org (Postfix) with ESMTP id 66EEF8FC15 for ; Sat, 17 Oct 2009 05:12:39 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii; format=flowed Received: from macbook-pro.lan.xcllnt.net (mail.xcllnt.net [75.101.29.67]) by asmtp027.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KRN005M4502E890@asmtp027.mac.com>; Fri, 16 Oct 2009 21:12:04 -0700 (PDT) From: Marcel Moolenaar In-reply-to: <200910161400.00564.jkim@FreeBSD.org> Date: Fri, 16 Oct 2009 21:12:02 -0700 Message-id: References: <20091015.085910.-520412456.imp@bsdimp.com> <4890688A-D2DB-431C-ADB6-03A39A8FD10E@mac.com> <200910161346.03066.jkim@FreeBSD.org> <200910161400.00564.jkim@FreeBSD.org> To: Jung-uk Kim X-Mailer: Apple Mail (2.1076) Cc: freebsd-arch@FreeBSD.org Subject: Re: x86BIOS and the ISA bus and low memory in general... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 05:12:39 -0000 On Oct 16, 2009, at 10:59 AM, Jung-uk Kim wrote: > > It seems pmap_mapdev() on ia64 uses IA64_PHYS_TO_RR6() macro. If I > read the source correctly, then it is gives UC mapped "view" of the > physical address, right? If so, orm(4) can simply do > pmap_mapdev()/pmap_unmapdev() around bus_space_read_region_1(). Am I > right? Not quite. pmap_mapdev() assumes that the passed physical address is valid. It not being a valid physical address was the pivotal problem and the reason why I limited orm(4) to i386 and amd64. -- Marcel Moolenaar xcllnt@mac.com