From owner-freebsd-arch@FreeBSD.ORG Mon Nov 29 06:01:25 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3844216A4CE for ; Mon, 29 Nov 2004 06:01:25 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F353A43D5E for ; Mon, 29 Nov 2004 06:01:24 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E741B72DF9; Sun, 28 Nov 2004 22:01:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E5F8572DCB; Sun, 28 Nov 2004 22:01:24 -0800 (PST) Date: Sun, 28 Nov 2004 22:01:24 -0800 (PST) From: Doug White To: Ursul Lodder In-Reply-To: <000801c4d2f1$913d9520$9600000a@MAINBOX> Message-ID: <20041128220110.H40277@carver.gumbysoft.com> References: <000801c4d2f1$913d9520$9600000a@MAINBOX> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@FreeBSD.org Subject: Re: FreeBSD on IBM 350-H ? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 06:01:25 -0000 On Thu, 25 Nov 2004, Ursul Lodder wrote: > Hi there at FreeBSD.org, is any of the versions of FReeBSD suitable to > use for installation on a IBM RS6000 (type 350-H)? Not at this time, no. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-arch@FreeBSD.ORG Tue Nov 30 18:03:22 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 778AC16A4CE for ; Tue, 30 Nov 2004 18:03:22 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5A7243D5A for ; Tue, 30 Nov 2004 18:03:21 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAUGYjUL050016; Tue, 30 Nov 2004 17:34:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ian Dowse From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 17 Nov 2004 23:22:56 GMT." <200411172322.aa34520@salmon.maths.tcd.ie> Date: Tue, 30 Nov 2004 17:34:45 +0100 Message-ID: <50015.1101832485@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: arch@freebsd.org Subject: Re: Simpler SMP-friendly callout/timeout semantics X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 18:03:22 -0000 In message <200411172322.aa34520@salmon.maths.tcd.ie>, Ian Dowse writes: > >The current callout/timeout API supports Giant-locked and MP-safe >usage options, but in both cases it is very difficult to use the >API in a way that is free of race conditions and complications. >Below is an attempt to extend that API to offer much simpler semantics >to many users while not limiting its usefulness or performance. > >Do people think that a change like this is worth attempting? Are >there further improvements that could be made or any other suggestions >or comments? Sounds good to me. Do you try to optimize softclock to not stall on the mutex and instead find any other pending callouts to handle ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Tue Nov 30 23:12:39 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31A6C16A4CE; Tue, 30 Nov 2004 23:12:39 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE27E43D48; Tue, 30 Nov 2004 23:12:38 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id C9B2CACADB; Wed, 1 Dec 2004 00:12:36 +0100 (CET) Date: Wed, 1 Dec 2004 00:12:36 +0100 From: Pawel Jakub Dawidek To: freebsd-arch@freebsd.org Message-ID: <20041130231236.GD56431@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hxkXGo8AKqTJ+9QI" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: cperciva@freebsd.org Subject: ps -e without procfs(5). X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 23:12:39 -0000 --hxkXGo8AKqTJ+9QI Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello. I need some testing for this patch: http://people.freebsd.org/~pjd/patches/ps-e.patch It allows to use 'ps -e' without procfs(5) mounted. I decided to disable this functionality by default, because procfs(5) is also disabled by default and some people may already depend on the fact, that environment is a secret by default. To see the effects, you need to increase sysctl kern.ps_env_cache_limit to for example 1024. Thanks in advance! --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --hxkXGo8AKqTJ+9QI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBrP5kForvXbEpPzQRAjMoAJ445A27IbMsmW+TcY5VIG/IE0+IAQCbBaHX THKF/RsBXBNnyuT59i8+4Tg= =2XGH -----END PGP SIGNATURE----- --hxkXGo8AKqTJ+9QI-- From owner-freebsd-arch@FreeBSD.ORG Wed Dec 1 00:28:06 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0649316A4CE; Wed, 1 Dec 2004 00:28:06 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3DD343D4C; Wed, 1 Dec 2004 00:28:05 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id C74D51977A; Tue, 30 Nov 2004 16:28:05 -0800 (PST) From: Peter Wemm To: freebsd-arch@freebsd.org Date: Tue, 30 Nov 2004 16:28:05 -0800 User-Agent: KMail/1.7.1 References: <20041130231236.GD56431@darkness.comp.waw.pl> In-Reply-To: <20041130231236.GD56431@darkness.comp.waw.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411301628.05476.peter@wemm.org> cc: Pawel Jakub Dawidek cc: cperciva@freebsd.org Subject: Re: ps -e without procfs(5). X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 00:28:06 -0000 On Tuesday 30 November 2004 03:12 pm, Pawel Jakub Dawidek wrote: > Hello. > > I need some testing for this patch: > > http://people.freebsd.org/~pjd/patches/ps-e.patch > > It allows to use 'ps -e' without procfs(5) mounted. > I decided to disable this functionality by default, because procfs(5) > is also disabled by default and some people may already depend on the > fact, that environment is a secret by default. > To see the effects, you need to increase sysctl > kern.ps_env_cache_limit to for example 1024. ps -e is "live" and reads the environment from the process. It looks like your patch adds a once-only snapshot of the exec-time values.. I've only ever used "ps -e" to figure out what the current live values are, I'd be more interested in a ptrace based replacement.. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-arch@FreeBSD.ORG Wed Dec 1 10:51:28 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8AD516A508; Wed, 1 Dec 2004 10:51:28 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62F9843D67; Wed, 1 Dec 2004 10:51:28 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 44E6DACC75; Wed, 1 Dec 2004 11:51:26 +0100 (CET) Date: Wed, 1 Dec 2004 11:51:26 +0100 From: Pawel Jakub Dawidek To: Peter Wemm Message-ID: <20041201105126.GB662@darkness.comp.waw.pl> References: <20041130231236.GD56431@darkness.comp.waw.pl> <200411301628.05476.peter@wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8P1HSweYDcXXzwPJ" Content-Disposition: inline In-Reply-To: <200411301628.05476.peter@wemm.org> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: cperciva@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: ps -e without procfs(5). X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 10:51:28 -0000 --8P1HSweYDcXXzwPJ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 30, 2004 at 04:28:05PM -0800, Peter Wemm wrote: +> ps -e is "live" and reads the environment from the process. It looks=20 +> like your patch adds a once-only snapshot of the exec-time values.. If you set environment variable you want it to be visible in 'ps -e' output before execve(2)? I don't see this behaviour even with procfs(5) mounted. Am I missing something? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --8P1HSweYDcXXzwPJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBraIuForvXbEpPzQRAn2pAJ479QRkdP8auz4/QeHFhzMDvVYNRACfeG1v l1nMRyLvnczQzfFhvtIeg0w= =tvNZ -----END PGP SIGNATURE----- --8P1HSweYDcXXzwPJ-- From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 18:07:02 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EB6E16A4EE for ; Fri, 3 Dec 2004 18:07:02 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C1A43D5A for ; Fri, 3 Dec 2004 18:07:01 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB3I4Ckx005307 for ; Fri, 3 Dec 2004 11:04:12 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 03 Dec 2004 11:05:20 -0700 (MST) Message-Id: <20041203.110520.54185564.imp@bsdimp.com> To: arch@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200412030813.iB38DA12044595@repoman.freebsd.org> References: <200412030813.iB38DA12044595@repoman.freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: src/sys/dev/pci pci.c X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 18:07:02 -0000 In message: <200412030813.iB38DA12044595@repoman.freebsd.org> Nate Lawson writes: : njl 2004-12-03 08:13:09 UTC : : FreeBSD src repository : : Modified files: : sys/dev/pci pci.c : Log: : Non-x86 platforms cannot use the ACPI includes. This should be fixed but : for now, only include the headers for i386, amd64, or ia64. : : Pointed out by: grehan We likely should have a sys/$MACHINE_ARCH/include/_config.h that has a bunch of #defines that we can test instead of specific architecture lists, don't you think? Warner From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 19:42:09 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E24A116A4CE for ; Fri, 3 Dec 2004 19:42:09 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5953843D31 for ; Fri, 3 Dec 2004 19:42:09 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB3Jg1e2016209; Fri, 3 Dec 2004 11:42:01 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iB3Jg1Oj016208; Fri, 3 Dec 2004 11:42:01 -0800 (PST) (envelope-from marcel) Date: Fri, 3 Dec 2004 11:42:01 -0800 From: Marcel Moolenaar To: "M. Warner Losh" Message-ID: <20041203194201.GB16093@ns1.xcllnt.net> References: <200412030813.iB38DA12044595@repoman.freebsd.org> <20041203.110520.54185564.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203.110520.54185564.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i cc: arch@freebsd.org Subject: Re: cvs commit: src/sys/dev/pci pci.c X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:42:10 -0000 On Fri, Dec 03, 2004 at 11:05:20AM -0700, M. Warner Losh wrote: > In message: <200412030813.iB38DA12044595@repoman.freebsd.org> > Nate Lawson writes: > : njl 2004-12-03 08:13:09 UTC > : > : FreeBSD src repository > : > : Modified files: > : sys/dev/pci pci.c > : Log: > : Non-x86 platforms cannot use the ACPI includes. This should be fixed but > : for now, only include the headers for i386, amd64, or ia64. > : > : Pointed out by: grehan > > We likely should have a sys/$MACHINE_ARCH/include/_config.h that has a > bunch of #defines that we can test instead of specific architecture > lists, don't you think? A doesn't give me warm fuzzies. Maybe we can rename to and give it some additional use (for this particular case of course). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 20:28:08 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E1FD16A4CE for ; Fri, 3 Dec 2004 20:28:08 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA26943D41 for ; Fri, 3 Dec 2004 20:28:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB3KPe4v007150; Fri, 3 Dec 2004 13:25:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 03 Dec 2004 13:26:50 -0700 (MST) Message-Id: <20041203.132650.04772724.imp@bsdimp.com> To: marcel@xcllnt.net From: "M. Warner Losh" In-Reply-To: <20041203194201.GB16093@ns1.xcllnt.net> References: <200412030813.iB38DA12044595@repoman.freebsd.org> <20041203.110520.54185564.imp@bsdimp.com> <20041203194201.GB16093@ns1.xcllnt.net> X-Mailer: Mew version 3.3 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: cvs commit: src/sys/dev/pci pci.c X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 20:28:08 -0000 In message: <20041203194201.GB16093@ns1.xcllnt.net> Marcel Moolenaar writes: : On Fri, Dec 03, 2004 at 11:05:20AM -0700, M. Warner Losh wrote: : > In message: <200412030813.iB38DA12044595@repoman.freebsd.org> : > Nate Lawson writes: : > : njl 2004-12-03 08:13:09 UTC : > : : > : FreeBSD src repository : > : : > : Modified files: : > : sys/dev/pci pci.c : > : Log: : > : Non-x86 platforms cannot use the ACPI includes. This should be fixed but : > : for now, only include the headers for i386, amd64, or ia64. : > : : > : Pointed out by: grehan : > : > We likely should have a sys/$MACHINE_ARCH/include/_config.h that has a : > bunch of #defines that we can test instead of specific architecture : > lists, don't you think? : : A doesn't give me warm fuzzies. Maybe we can : rename to and give it some : additional use (for this particular case of course). There's a growing number of these sorts of things. NetBSD has this information in machine/types.h. For example: #include #define __HAVE_GENERIC_SOFT_INTERRUPTS #define __HAVE_DEVICE_REGISTER #define __HAVE_NWSCONS #define __HAVE_MIPS_MACHDEP_CACHE_CONFIG I was thinking that we should start doing something similar... Warner From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 20:50:47 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCEDE16A4CE for ; Fri, 3 Dec 2004 20:50:47 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 604C943D2D for ; Fri, 3 Dec 2004 20:50:47 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB3KoexI016681; Fri, 3 Dec 2004 12:50:41 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iB3KoelO016680; Fri, 3 Dec 2004 12:50:40 -0800 (PST) (envelope-from marcel) Date: Fri, 3 Dec 2004 12:50:40 -0800 From: Marcel Moolenaar To: "M. Warner Losh" Message-ID: <20041203205040.GA16617@ns1.xcllnt.net> References: <200412030813.iB38DA12044595@repoman.freebsd.org> <20041203.110520.54185564.imp@bsdimp.com> <20041203194201.GB16093@ns1.xcllnt.net> <20041203.132650.04772724.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203.132650.04772724.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i cc: arch@freebsd.org Subject: Re: cvs commit: src/sys/dev/pci pci.c X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 20:50:48 -0000 On Fri, Dec 03, 2004 at 01:26:50PM -0700, M. Warner Losh wrote: > : > We likely should have a sys/$MACHINE_ARCH/include/_config.h that has a > : > bunch of #defines that we can test instead of specific architecture > : > lists, don't you think? > : > : A doesn't give me warm fuzzies. Maybe we can > : rename to and give it some > : additional use (for this particular case of course). > > There's a growing number of these sorts of things. NetBSD has this > information in machine/types.h. For example: > > #include > > #define __HAVE_GENERIC_SOFT_INTERRUPTS > #define __HAVE_DEVICE_REGISTER > #define __HAVE_NWSCONS > > #define __HAVE_MIPS_MACHDEP_CACHE_CONFIG > > I was thinking that we should start doing something similar... For some reason I have a bad feeling about this. It's soooo easily misused. For one, it's a good way to cover up a bad design or an incomplete implementation. It goes no further than a feeling though. There's nothing wrong with it in principle, because differences do exist. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 21:22:57 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A968316A4CE for ; Fri, 3 Dec 2004 21:22:57 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 039C543D55 for ; Fri, 3 Dec 2004 21:22:57 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB3LMuqV026128 for ; Fri, 3 Dec 2004 22:22:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org From: "Poul-Henning Kamp" Date: Fri, 03 Dec 2004 22:22:56 +0100 Message-ID: <26127.1102108976@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [HEADSUP] omount/nmount migration and rootfs mounting X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 21:22:57 -0000 Ok, here is the big picture: All filesystems get a ->vfs_mount() which does the job. Filesystems which have a ->vfs_omount() looses it and gets a ->vfs_cmount() instead which after pulling compat args in calls the nmount() stuff. Here is my prototype for ffs: +static int +ffs_cmount(char *path, void *data, int flags, struct thread *td) +{ + struct ufs_args args; + struct iovec v[10]; + int error; + + if (data == NULL) + return (EINVAL); + error = copyin(data, &args, sizeof args); + if (error) + return (error); + + v[0].iov_base = "fstype"; + v[0].iov_len = strlen(v[0].iov_base) + 1; + v[1].iov_base = "ufs"; + v[1].iov_len = strlen(v[1].iov_base) + 1; + + v[2].iov_base = "fspath"; + v[2].iov_len = strlen(v[2].iov_base) + 1; + v[3].iov_base = path; + v[3].iov_len = strlen(v[3].iov_base) + 1; + + v[4].iov_base = "from"; + v[4].iov_len = strlen(v[4].iov_base) + 1; + v[5].iov_base = args.fspec; + v[5].iov_len = strlen(v[5].iov_base) + 1; + + v[6].iov_base = "export"; + v[6].iov_len = strlen(v[6].iov_base) + 1; + v[7].iov_base = &args.export; + v[7].iov_len = sizeof(args.export); + + v[8].iov_base = NULL; + v[8].iov_len = 0; + + error = kernel_mount(v, 8, flags); + + return (error); +} Root mounting will happen the following way: create a mountpoint. devfs->vfs_mount() on it. set rootdir for proc0 create symlink: /dev -> / Mount real root filesystem as / using normal ->vfs_mount() method. (filesystem contains no magic for this) Surgically move the devfs mount from / to /dev in the new rootfs. Keep an eye on p4:phk_bufwork, it works for ffs and nfs already. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-arch@FreeBSD.ORG Fri Dec 3 21:40:03 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9186316A4CE for ; Fri, 3 Dec 2004 21:40:03 +0000 (GMT) Received: from fidel.freesurf.fr (fidel.freesurf.fr [212.43.206.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5396443D53 for ; Fri, 3 Dec 2004 21:40:03 +0000 (GMT) (envelope-from nsouch@free.fr) Received: from smtp (62-240-249-21.adsl.freesurf.fr [62.240.249.21]) by fidel.freesurf.fr (Postfix) with SMTP id 1EA6A2A70C0 for ; Fri, 3 Dec 2004 22:40:02 +0100 (CET) Received: (qmail 2195 invoked by uid 1000); 3 Dec 2004 21:40:01 -0000 Date: Fri, 3 Dec 2004 22:40:01 +0100 From: Nicolas Souchu To: freebsd-arch@freebsd.org Message-ID: <20041203214000.GA1466@breizh> References: <20041112074922.GA727@loge.nixsys.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041112074922.GA727@loge.nixsys.be> User-Agent: Mutt/1.5.6+20040722i Subject: Re: Generic 'input device' layer X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 21:40:03 -0000 On Fri, Nov 12, 2004 at 08:49:22AM +0100, Philip Paeps wrote: > I've been spending the last few weeks writing and hacking touchscreen drivers > in the Linux kernel for one of my clients. Thanks to the simple 'input core' > framework, this was pretty easy to do. It wasn't fun, but it was easy. > > Trying to port these drivers to FreeBSD is a lot more painful than it should > be, and I'm finding myself duplicating heaps of code (translating absolute > coordinates to dx/dy motions, mapping buttons, etc). > > Has anyone else tried to write something like 'input core' for FreeBSD? A > quick Google doesn't turn up anything of particular interest. > > Basically, I'm looking for a way to get from hardware events to something > syscons will understand, without having to do all sorts of really disgusting > magic in sys/isa/psm.c or usr.sbin/moused/moused.c. > > If no one else is working on this, I'd like to solicit ideas for what others > would like this interface to look like, and I'll go and write it myself :-) > > Ideas are welcome! http://www.ggi-project.org Is the userland side of such a library. http://www.freebsd.org/~nsouch/kgi4BSD Is an attempt to have KGI the kernel side of GGI under FreeBSD. Have you ever heard about GGI? You should start from it before KGI. Nicholas