From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 04:41:51 2008 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 9C6D71065672 for ; Sun, 7 Sep 2008 04:41:51 +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 4A4218FC14 for ; Sun, 7 Sep 2008 04:41:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m874dhSI046152 for ; Sat, 6 Sep 2008 22:39:43 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 06 Sep 2008 22:40:18 -0600 (MDT) Message-Id: <20080906.224018.-1303464793.imp@bsdimp.com> To: arch@FreeBSD.org From: "M. Warner Losh" 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: Subject: pax in /rescue 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: Sun, 07 Sep 2008 04:41:51 -0000 Is there any reason to continue to include both tar and pax in /rescue? Warner From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 05:20:17 2008 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 16006106564A for ; Sun, 7 Sep 2008 05:20:17 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id CD7968FC14 for ; Sun, 7 Sep 2008 05:20:16 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id m8754AhW011484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Sep 2008 01:04:10 -0400 (EDT) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: "M. Warner Losh" In-Reply-To: <20080906.224018.-1303464793.imp@bsdimp.com> References: <20080906.224018.-1303464793.imp@bsdimp.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tn97nH2oNT/qzNWtCCLS" Organization: U. Buffalo CSE Department Date: Sun, 07 Sep 2008 01:04:09 -0400 Message-Id: <1220763849.29265.47.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1335; Body=0 Fuz1=0 Fuz2=0 Cc: arch@freebsd.org Subject: Re: pax in /rescue 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: Sun, 07 Sep 2008 05:20:17 -0000 --=-tn97nH2oNT/qzNWtCCLS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2008-09-06 at 22:40 -0600, M. Warner Losh wrote: > Is there any reason to continue to include both tar and pax in > /rescue? JFYI - despite the cpio/sysinstall issues apparently being fixed I'm still planning to switch sysinstall over to using tar. I know that's not what you're "directly" asking about but it's at least "remotely related" depending on peoples' feelings about which of the two should be removed if the answer to your question is "No". --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-tn97nH2oNT/qzNWtCCLS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkjDYMkACgkQ/G14VSmup/aHtgCbBgdz+s+IZ3MiO+0FJp8mHsu4 iyEAoIwXTjL0LqzkxsJZBq+guyTO+3CP =nCVp -----END PGP SIGNATURE----- --=-tn97nH2oNT/qzNWtCCLS-- From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 05:45:07 2008 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 AAE51106567A for ; Sun, 7 Sep 2008 05:45:07 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188]) by mx1.freebsd.org (Postfix) with ESMTP id 2D9A58FC19 for ; Sun, 7 Sep 2008 05:45:06 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so593220tid.3 for ; Sat, 06 Sep 2008 22:45:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=cFNZWONL/NVu0imlyF1IaGEUuO830Sl5ptd1tUBSiNI=; b=l8/1EPXavI449hpjAioPIOAFX6HEMy/lkyLL9BL1/eiF8QSnhF88IptshQS2HnJLAC MaUH+KpZz1ECkPZdzuURMhMutfALz14Q5VAoDr4crwteuy+kec7j6RJEVvGlnTvC9Urf C2fwukZPhtYKMHA6fUXiSAZIgrIBSqQWDbFU4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=FoLhfO4lpCMeRmFY/EN4mUtKomuLw1ZS0nwryI90WlR3TwF5VCIHFyWhqCBZtoWhww +Z+JqYw8UKnPlrQBfZeKqGXe+lTXpJDY9f5X6Va5F0QV/hetyQwz81vPG64O8bCNhZFO ib8V0S2GbixJjAAofPNaqi3n3G272e9wzL3xQ= Received: by 10.110.15.9 with SMTP id 9mr17801600tio.50.1220764965069; Sat, 06 Sep 2008 22:22:45 -0700 (PDT) Received: by 10.110.63.8 with HTTP; Sat, 6 Sep 2008 22:22:44 -0700 (PDT) Message-ID: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> Date: Sun, 7 Sep 2008 13:22:44 +0800 From: chinsan To: "M. Warner Losh" In-Reply-To: <20080906.224018.-1303464793.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080906.224018.-1303464793.imp@bsdimp.com> Cc: arch@freebsd.org Subject: Re: pax in /rescue 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: Sun, 07 Sep 2008 05:45:07 -0000 On Sun, Sep 7, 2008 at 12:40 PM, M. Warner Losh wrote: > Is there any reason to continue to include both tar and pax in > /rescue? > Maybe for rescue some important file? BTW, could editors/e3 be include into /rescue? I think it's ineed to have a text editor to edit some file for rescue. Because vi(1) lives in /usr/bin. ps. e3 is a full featured text editor written in NASM assembler. It is highly optimized for size. From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 05:57:05 2008 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 82888106568A for ; Sun, 7 Sep 2008 05:57:05 +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 415748FC17 for ; Sun, 7 Sep 2008 05:57:05 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m875tvt7046889; Sat, 6 Sep 2008 23:55:58 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 06 Sep 2008 23:56:33 -0600 (MDT) Message-Id: <20080906.235633.-267228782.imp@bsdimp.com> To: chinsan.tw@gmail.com From: "M. Warner Losh" In-Reply-To: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> 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: pax in /rescue 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: Sun, 07 Sep 2008 05:57:05 -0000 In message: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> chinsan writes: : On Sun, Sep 7, 2008 at 12:40 PM, M. Warner Losh wrote: : > Is there any reason to continue to include both tar and pax in : > /rescue? : > : Maybe for rescue some important file? tar can read all the formats that pax can read. Why the duplication in functionality? : BTW, could editors/e3 be include into /rescue? : I think it's ineed to have a text editor to edit some file for rescue. : Because vi(1) lives in /usr/bin. /rescue already has nvi. : ps. e3 is a full featured text editor written in NASM assembler. It is highly : optimized for size. I notice pax was there when I was looking at it on my FreeBSD/arm box :-) Warner From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 06:12:14 2008 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 A195F106566C for ; Sun, 7 Sep 2008 06:12:14 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188]) by mx1.freebsd.org (Postfix) with ESMTP id 29A128FC13 for ; Sun, 7 Sep 2008 06:12:13 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so596561tid.3 for ; Sat, 06 Sep 2008 23:12:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=RerNwIc74rbZWCegNRmEojwov6m73r8m3Ocm67m2oZc=; b=nzAViwditm7nmXagxt1zCrAvKSSrANXvWePi+HfjkIKqAgLAIkA1QeOjnhe3oe9EeQ uTcgADOERT/fn6zxpmGiEqA4Yc6Vqd1vCgLyHIAflpB0MbJaYSC5yCjIdtDq/H8BwEK1 tEAhuVyp+TTYTQg7BQBYY9HfRgJxSeoVsb+nQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=K3rhSYxg5QONEVWj1WFVrejVStagz06y3vcuey/TJM9Ao4PMX52XRDQVQ5Yoib+1Mz LvFUUGRH1DZFJONivqo/gJawCHYNxi1shrGqNP9V4Ypv+7HzMFyVAyE+1fMOaU2ngaYl RfzgkWWbTYHC/8Xgi4EeGGKBktPxPEZTSVklw= Received: by 10.110.109.12 with SMTP id h12mr17846088tic.51.1220767932960; Sat, 06 Sep 2008 23:12:12 -0700 (PDT) Received: by 10.110.63.8 with HTTP; Sat, 6 Sep 2008 23:12:12 -0700 (PDT) Message-ID: <1f27304c0809062312x7656c379gcd994be9fc0ca3e2@mail.gmail.com> Date: Sun, 7 Sep 2008 14:12:12 +0800 From: chinsan To: "M. Warner Losh" In-Reply-To: <20080906.235633.-267228782.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> <20080906.235633.-267228782.imp@bsdimp.com> Cc: arch@freebsd.org Subject: Re: pax in /rescue 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: Sun, 07 Sep 2008 06:12:14 -0000 On Sun, Sep 7, 2008 at 1:56 PM, M. Warner Losh wrote: > In message: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> > chinsan writes: > : On Sun, Sep 7, 2008 at 12:40 PM, M. Warner Losh wrote: > : > Is there any reason to continue to include both tar and pax in > : > /rescue? > : > > : Maybe for rescue some important file? > > tar can read all the formats that pax can read. Why the duplication > in functionality? Oh, you are right. :p > > : BTW, could editors/e3 be include into /rescue? > : I think it's ineed to have a text editor to edit some file for rescue. > : Because vi(1) lives in /usr/bin. > > /rescue already has nvi. But nvi needs terminfo(5), so it needs to mount /usr filesystem too. From owner-freebsd-arch@FreeBSD.ORG Sun Sep 7 13:59:43 2008 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 99DCF106564A for ; Sun, 7 Sep 2008 13:59:43 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx09.syd.optusnet.com.au (fallbackmx09.syd.optusnet.com.au [211.29.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 1CB738FC1B for ; Sun, 7 Sep 2008 13:59:42 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au [211.29.133.51]) by fallbackmx09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m87AnSbu024498 for ; Sun, 7 Sep 2008 20:49:28 +1000 Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m87AnPas027101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Sep 2008 20:49:25 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m87AnOKx046672; Sun, 7 Sep 2008 20:49:24 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m87AnOri046671; Sun, 7 Sep 2008 20:49:24 +1000 (EST) (envelope-from peter) Date: Sun, 7 Sep 2008 20:49:24 +1000 From: Peter Jeremy To: chinsan Message-ID: <20080907104924.GZ15376@server.vk2pj.dyndns.org> References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> <20080906.235633.-267228782.imp@bsdimp.com> <1f27304c0809062312x7656c379gcd994be9fc0ca3e2@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9Q2l3mYpK16UQ/iv" Content-Disposition: inline In-Reply-To: <1f27304c0809062312x7656c379gcd994be9fc0ca3e2@mail.gmail.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: arch@freebsd.org Subject: Re: pax in /rescue 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: Sun, 07 Sep 2008 13:59:43 -0000 --9Q2l3mYpK16UQ/iv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Sep-07 14:12:12 +0800, chinsan wrote: >But nvi needs terminfo(5), so it needs to mount /usr filesystem too. There was a discussion on this point in -current in early August. I don't think there's a need to re-hash it here. See http://lists.freebsd.org/pipermail/freebsd-current/2008-August/087355.h= tml --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --9Q2l3mYpK16UQ/iv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjDsbQACgkQ/opHv/APuIc8vQCfYjB8/90MB9ww9vKk5QRJ962K L80AnjkFWNseaSaedRRTA0kHRA/+8ZUG =gbHn -----END PGP SIGNATURE----- --9Q2l3mYpK16UQ/iv-- From owner-freebsd-arch@FreeBSD.ORG Mon Sep 8 02:22:17 2008 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 D65E8106566B for ; Mon, 8 Sep 2008 02:22:17 +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 C46A38FC15 for ; Mon, 8 Sep 2008 02:22:17 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m882MHaD006621 for ; Mon, 8 Sep 2008 02:22:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m882MHOG006617 for freebsd-arch@FreeBSD.org; Mon, 8 Sep 2008 02:22:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Sep 2008 02:22:17 GMT Message-Id: <200809080222.m882MHOG006617@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, 08 Sep 2008 02:22:17 -0000 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. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. From owner-freebsd-arch@FreeBSD.ORG Mon Sep 8 09:46:46 2008 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 E72AC1065671 for ; Mon, 8 Sep 2008 09:46:46 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mx1.freebsd.org (Postfix) with ESMTP id 3932B8FC18 for ; Mon, 8 Sep 2008 09:46:45 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A5742.dip.t-dialin.net [84.154.87.66]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m889Ps2H085945; Mon, 8 Sep 2008 11:25:56 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m889Phr5050093; Mon, 8 Sep 2008 11:25:43 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m889PRLA083055; Mon, 8 Sep 2008 11:25:32 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200809080925.m889PRLA083055@fire.js.berklix.net> To: chinsan From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Sun, 07 Sep 2008 13:22:44 +0800." <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> Date: Mon, 08 Sep 2008 11:25:27 +0200 Sender: jhs@berklix.org Cc: arch@freebsd.org Subject: Re: pax in /rescue 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, 08 Sep 2008 09:46:47 -0000 Hi, Reference: > From: chinsan > Date: Sun, 7 Sep 2008 13:22:44 +0800 > Message-id: <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> chinsan wrote: > On Sun, Sep 7, 2008 at 12:40 PM, M. Warner Losh wrote: > > Is there any reason to continue to include both tar and pax in > > /rescue? > > > Maybe for rescue some important file? > BTW, could editors/e3 be include into /rescue? > I think it's ineed to have a text editor to edit some file for rescue. > Because vi(1) lives in /usr/bin. No, use ed, ed has been in Unix 30+ years. /bin/ed > ps. e3 is a full featured text editor written in NASM assembler. It is highly > optimized for size. No, FreeBSD is not just i386. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From owner-freebsd-arch@FreeBSD.ORG Mon Sep 8 18:50:13 2008 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 C0BA51065671 for ; Mon, 8 Sep 2008 18:50:13 +0000 (UTC) (envelope-from rcoleman@criticalmagic.com) Received: from smtp-auth.no-ip.com (smtp-auth.no-ip.com [204.16.252.95]) by mx1.freebsd.org (Postfix) with ESMTP id AB2EC8FC1A for ; Mon, 8 Sep 2008 18:50:13 +0000 (UTC) (envelope-from rcoleman@criticalmagic.com) X-No-IP: criticalmagic.com@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from [172.30.1.103] (fw1-e0-2.dth.xiocom.net [69.71.237.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: criticalmagic.com@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTP id CE4501AA9FF for ; Mon, 8 Sep 2008 11:26:10 -0700 (PDT) Message-ID: <48C56E41.40002@criticalmagic.com> Date: Mon, 08 Sep 2008 14:26:09 -0400 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: arch@freebsd.org References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> <20080906.235633.-267228782.imp@bsdimp.com> In-Reply-To: <20080906.235633.-267228782.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: pax in /rescue 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, 08 Sep 2008 18:50:13 -0000 M. Warner Losh wrote: > : BTW, could editors/e3 be include into /rescue? > : I think it's ineed to have a text editor to edit some file for rescue. > : Because vi(1) lives in /usr/bin. > > /rescue already has nvi. But this is only partially useful until the root partition/termcap issue is finally fixed. It comes up on the list about every 6 months, and everyone says "yeah, we should move the termcap file". And that's where it sits until the topic comes up again in another 6 months :-) Richard Coleman rcoleman@criticalmagic.com From owner-freebsd-arch@FreeBSD.ORG Tue Sep 9 16:50:18 2008 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 C29631065674 for ; Tue, 9 Sep 2008 16:50:18 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 267368FC13 for ; Tue, 9 Sep 2008 16:50:17 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl21-99.kln.forthnet.gr [77.49.148.99]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id m89GdNkq021085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Sep 2008 19:39:29 +0300 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id m89GdMEh003412; Tue, 9 Sep 2008 19:39:22 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id m89GdLHf003411; Tue, 9 Sep 2008 19:39:21 +0300 (EEST) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: Richard Coleman References: <20080906.224018.-1303464793.imp@bsdimp.com> <1f27304c0809062222m724603dat2fb1af63dba5faa6@mail.gmail.com> <20080906.235633.-267228782.imp@bsdimp.com> <48C56E41.40002@criticalmagic.com> Date: Tue, 09 Sep 2008 19:39:21 +0300 In-Reply-To: <48C56E41.40002@criticalmagic.com> (Richard Coleman's message of "Mon, 08 Sep 2008 14:26:09 -0400") Message-ID: <87ej3tnuiu.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: m89GdNkq021085 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.29, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.11, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: arch@freebsd.org Subject: Re: pax in /rescue 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, 09 Sep 2008 16:50:18 -0000 On Mon, 08 Sep 2008 14:26:09 -0400, Richard Coleman wrote: > M. Warner Losh wrote: >> : BTW, could editors/e3 be include into /rescue? >> : I think it's ineed to have a text editor to edit some file for rescue. >> : Because vi(1) lives in /usr/bin. >> >> /rescue already has nvi. > > But this is only partially useful until the root partition/termcap issue > is finally fixed. > > It comes up on the list about every 6 months, and everyone says "yeah, > we should move the termcap file". And that's where it sits until the > topic comes up again in another 6 months :-) I'm working on it. The ideas from the last discussion about allowing a minimal termcap in the root filesystem, and modifying ncurses to look for that as a fallback are nice... See the thread in freebsd-current that includes the posts: !A 2008-08-05 [ 28: Alex Kozlov ] Re: termcap under single luser ! 2008-08-06 [ 32: Alex Kozlov ] Re: termcap under single luser From owner-freebsd-arch@FreeBSD.ORG Wed Sep 10 20:13:22 2008 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 D0F67106567F for ; Wed, 10 Sep 2008 20:13:22 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 706DD8FC2D for ; Wed, 10 Sep 2008 20:13:22 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8AKDFEm022214 for ; Wed, 10 Sep 2008 16:13:16 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: arch@FreeBSD.org Date: Wed, 10 Sep 2008 15:31:54 -0400 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809101531.54646.jhb@FreeBSD.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 10 Sep 2008 16:13:16 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8211/Wed Sep 10 15:01:28 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Subject: PASSERT() - asserting for panics 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, 10 Sep 2008 20:13:22 -0000 So one of the things I like to do is use kernel modules that do regression tests. One of the things I want to test is that certain invalid operations will cause a specific panic. In the past I've done nefarious things like '#define panic printf' at the top of kern_rwlock.c and such. :) However, this is not suitable for more widespread use. The other approach of having the tests panic and verifying the panics that way is tedious. So what I came up with is a way to assert that a given panic will be triggered by a chunk of code, and if that panic happens, the kernel doesn't actually panic. The way I implemented this was by having the actual test do a setjmp() and if the "expected" panic triggers, then panic() does a longjmp() before setting panicstr, etc. A simple example of using it would be: PASSERT("foo", panic("foo")); The patch is at http://www.FreeBSD.org/~jhb/patches/passert.patch and below: --- //depot/projects/smpng/sys/kern/kern_shutdown.c 2008/03/18 12:54:14 +++ //depot/user/jhb/lock/kern/kern_shutdown.c 2008/09/10 17:40:44 @@ -531,6 +531,17 @@ if (panicstr) bootopt |= RB_NOSYNC; else { +#ifdef INVARIANT_SUPPORT + if (td->td_expected_panic != NULL && + strcmp(td->td_expected_panic, fmt) == 0) { + va_start(ap, fmt); + printf("expected panic: "); + vprintf(fmt, ap); + printf("\n"); + va_end(ap); + longjmp(td->td_panic_buf, 1); + } +#endif panicstr = fmt; newpanic = 1; } --- //depot/projects/smpng/sys/kern/kern_thread.c 2008/08/25 16:33:41 +++ //depot/user/jhb/lock/kern/kern_thread.c 2008/09/09 18:31:16 @@ -35,6 +35,7 @@ #include #include #include +#include #include #include #include @@ -48,6 +49,7 @@ #include #include +#include #include #include @@ -161,6 +163,9 @@ td->td_sched = (struct td_sched *)&td[1]; umtx_thread_init(td); td->td_kstack = 0; +#ifdef INVARIANT_SUPPORT + td->td_panic_buf = malloc(sizeof(struct _jmp_buf), M_SUBPROC, M_WAITOK); +#endif return (0); } @@ -178,6 +183,9 @@ sleepq_free(td->td_sleepqueue); umtx_thread_fini(td); seltdfini(td); +#ifdef INVARIANT_SUPPORT + free(td->td_panic_buf, M_SUBPROC); +#endif } /* --- //depot/projects/smpng/sys/sys/proc.h 2008/08/25 16:33:41 +++ //depot/user/jhb/lock/sys/proc.h 2008/09/09 18:31:16 @@ -166,6 +166,7 @@ struct kdtrace_proc; struct kdtrace_thread; struct cpuset; +struct _jmp_buf; /* * Kernel runnable context (thread). @@ -273,6 +274,8 @@ struct lpohead td_lprof[2]; /* (a) lock profiling objects. */ struct kdtrace_thread *td_dtrace; /* (*) DTrace-specific data. */ int td_errno; /* Error returned by last syscall. */ + struct _jmp_buf *td_panic_buf; /* (k) Jump buffer for PASSERT(). */ + const char *td_expected_panic; /* (k) Expected panic. */ }; struct mtx *thread_lock_block(struct thread *); --- //depot/projects/smpng/sys/sys/systm.h 2008/07/25 18:20:23 +++ //depot/user/jhb/lock/sys/systm.h 2008/09/09 18:31:16 @@ -71,9 +71,25 @@ if (__predict_false(!(exp))) \ panic msg; \ } while (0) + +#define PASSERT(panicstr, code) do { \ + switch (setjmp(curthread->td_panic_buf)) { \ + case 0: \ + curthread->td_expected_panic = (panicstr); \ + code; \ + panic("Expected panic '%s' did not trigger", \ + (panicstr)); \ + case 1: \ + curthread->td_expected_panic = NULL; \ + break; \ + default: \ + panic("Unexpected return value from setjmp()"); \ + } \ +} while (0) + #define VNASSERT(exp, vp, msg) do { \ if (__predict_false(!(exp))) { \ vn_printf(vp, "VNASSERT failed\n"); \ panic msg; \ } \ } while (0) @@ -81,6 +97,9 @@ #define KASSERT(exp,msg) do { \ } while (0) +#define PASSERT(panicstr, code) do { \ +} while (0) + #define VNASSERT(exp, vp, msg) do { \ } while (0) #endif Is this too evil for the tree? -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Wed Sep 10 21:37:41 2008 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 DADE01065672; Wed, 10 Sep 2008 21:37:41 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id A2DE08FC1C; Wed, 10 Sep 2008 21:37:41 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m8ALQxMw032025; Wed, 10 Sep 2008 14:26:59 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m8ALQxdK032024; Wed, 10 Sep 2008 14:26:59 -0700 (PDT) Date: Wed, 10 Sep 2008 14:26:59 -0700 (PDT) From: Matthew Dillon Message-Id: <200809102126.m8ALQxdK032024@apollo.backplane.com> To: John Baldwin References: <200809101531.54646.jhb@FreeBSD.org> Cc: arch@freebsd.org Subject: Re: PASSERT() - asserting for panics 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, 10 Sep 2008 21:37:41 -0000 : PASSERT("foo", panic("foo")); : :The patch is at http://www.FreeBSD.org/~jhb/patches/passert.patch and below: :.. The general problem with creating a more complex style of assertion is, well, that it is more complex. As a programmer who adds assertions all over the place (HAMMER has 343 KKASSERTs, for example), the last thing I want to do is to have to think about the assertion line itself or have to read through the visual pollution. Most of the time I just want to KKASSERT(condition) and be done with it. I would consider using a DATASET (easily embedded in a statement as it is a static declaration) to back the assertion macro and then simplify it to just: PASSERT(label, condition) The kernel would collect the DATASETs together and provide a sysctl API to allow the action taken to be managed at run-time based on the label. You could even have a version that doesn't use a label at all and is instead indexed by file and line. The output would be the stringtized condition (similar to libc's assert(cond) or DFly's KKASSERT(cond)). You could also have an optional macro to specify a default action for the label, and a master global sysctl to override everything. The actual code generated would simply be the conditional and, say, a call to _passert(&dataset), reducing code pollution as well as visual pollution. I have considered doing something similar in DragonFly for KKASSERT to reduce the code generated by the multi-argument panic() it calls. -Matt From owner-freebsd-arch@FreeBSD.ORG Wed Sep 10 22:35:39 2008 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 936741065673 for ; Wed, 10 Sep 2008 22:35:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 27FE58FC26 for ; Wed, 10 Sep 2008 22:35:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8AMZRd8023735; Wed, 10 Sep 2008 18:35:28 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Matthew Dillon Date: Wed, 10 Sep 2008 18:06:37 -0400 User-Agent: KMail/1.9.7 References: <200809101531.54646.jhb@FreeBSD.org> <200809102126.m8ALQxdK032024@apollo.backplane.com> In-Reply-To: <200809102126.m8ALQxdK032024@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809101806.38042.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 10 Sep 2008 18:35:28 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8212/Wed Sep 10 16:19:49 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: arch@freebsd.org Subject: Re: PASSERT() - asserting for panics 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, 10 Sep 2008 22:35:39 -0000 On Wednesday 10 September 2008 05:26:59 pm Matthew Dillon wrote: > : PASSERT("foo", panic("foo")); > : > :The patch is at http://www.FreeBSD.org/~jhb/patches/passert.patch and below: > :.. > > The general problem with creating a more complex style of assertion > is, well, that it is more complex. As a programmer who adds assertions > all over the place (HAMMER has 343 KKASSERTs, for example), the last > thing I want to do is to have to think about the assertion line itself > or have to read through the visual pollution. Most of the time I just > want to KKASSERT(condition) and be done with it. > > I would consider using a DATASET (easily embedded in a statement as it > is a static declaration) to back the assertion macro and then simplify > it to just: > > PASSERT(label, condition) > > The kernel would collect the DATASETs together and provide a sysctl > API to allow the action taken to be managed at run-time based on the > label. You could even have a version that doesn't use a label at all > and is instead indexed by file and line. The output would be the > stringtized condition (similar to libc's assert(cond) or DFly's > KKASSERT(cond)). You could also have an optional macro to specify > a default action for the label, and a master global sysctl to override > everything. > > The actual code generated would simply be the conditional and, say, > a call to _passert(&dataset), reducing code pollution as well as visual > pollution. I have considered doing something similar in DragonFly for > KKASSERT to reduce the code generated by the multi-argument panic() > it calls. I think part of the pollution is that what I really want to do is treat a panic like an exception that I can catch. I could probably make that idiom work with two macros so your code can be: PASSERT_BEGIN("foo") { /* do stuff */ } PASSERT_END; It would be more like exceptions in C++ though to have the string at the end: PANIC_TRY { /* do stuff */ } PANIC_CATCH("foo"); That could potentially work with some evil goto's that jumped between the macros (i.e. have the setjmp() in PANIC_CATCH and PANIC_TRY goto's down to that and then CATCH goto's back to TRY when setjmp returns 0), but those would be gross. The other problem is that you would probably be limited to a single TRY/CATCH per function, and I actually have some existing regression tests that do multiple potential panics in a single routine. -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Thu Sep 11 00:06:57 2008 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 9B0791065678; Thu, 11 Sep 2008 00:06:57 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 66A0D8FC1A; Thu, 11 Sep 2008 00:06:57 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m8B06vGD033200; Wed, 10 Sep 2008 17:06:57 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.14.1/8.13.4/Submit) id m8B06vOU033199; Wed, 10 Sep 2008 17:06:57 -0700 (PDT) Date: Wed, 10 Sep 2008 17:06:57 -0700 (PDT) From: Matthew Dillon Message-Id: <200809110006.m8B06vOU033199@apollo.backplane.com> To: John Baldwin References: <200809101531.54646.jhb@FreeBSD.org> <200809102126.m8ALQxdK032024@apollo.backplane.com> <200809101806.38042.jhb@freebsd.org> Cc: arch@freebsd.org Subject: Re: PASSERT() - asserting for panics 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, 11 Sep 2008 00:06:57 -0000 :I think part of the pollution is that what I really want to do is treat a :panic like an exception that I can catch. I could probably make that idiom :work with two macros so your code can be: : : PANIC_TRY { : /* do stuff */ : } PANIC_CATCH("foo"); : :That could potentially work with some evil goto's that jumped between the :macros (i.e. have the setjmp() in PANIC_CATCH and PANIC_TRY goto's down to :-- :John Baldwin Hmm. Almost java-like, where an exception pops back through subroutine levels until it finds a match. That kind of functionality would be a real mess in C. A limited form would be possible, something like this: #define PANIC_CATCH(label) \ (...) static jmpbuf label # _jmpbuf if (0) { for (;;) { longjmp(&label # _jmpbuf); label: #define PANIC_RETRY }} #define PANIC_PANIC panic(...); }} #define PASSERT(label, cond) \ (...) if (__predict_false(!(cond))) { setjmp (&label # _jmpbuf); goto label; } PANIC_CATCH(badthings) { ... PANIC_RETRY; } PANIC_CATCH(badthings) { ... PANIC_PANIC; } PASSERT(badthings, x == 1); Which would allow you some control over the context plus allow multiple PASSERT's with the same label. But, OMG I don't know about doing setjmp/longjmp in the kernel. I don't think it would be worth it. Theoretically one could cross procedural boundaries with the longjmp, and place the jmpbuf in a DATASET and have the kernel glue the longjmp address. That would be a candidate for the C obfuscation contest though. -Matt Matthew Dillon From owner-freebsd-arch@FreeBSD.ORG Thu Sep 11 17:55:58 2008 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 9DD26106564A for ; Thu, 11 Sep 2008 17:55:58 +0000 (UTC) (envelope-from mehulc87@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id 5C4058FC18 for ; Thu, 11 Sep 2008 17:55:58 +0000 (UTC) (envelope-from mehulc87@gmail.com) Received: by wx-out-0506.google.com with SMTP id s17so222595wxc.7 for ; Thu, 11 Sep 2008 10:55:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=hwUbwJTgqhKZkn3xGMRCAeLeaKcPYf4hEQtE6107HtA=; b=CdmYhL54f+oCvKz6TGlXuPeGP7pmVFlT5IqJ+Q6a0J3MhesBgGU8wVKsv96rEA2CsL KdPnElW4yqdgBZG6VtkGfxjP0IBamhTtaKDCFKpelljZrv8PCnPCkLZoPS2Bw45z4dGJ gRIvjyjuHrh5bImzSysyYZqbNivgbOvWeY7GQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=kQAJk5RMgy2/vs9ELHP9EjiCJ9rkdEALv8v9ZRZtX0jEveAFHdBBpY2z5RzRqZRN/u 5A2eMMVSumG3aA5PhGcyyr/nO0nUC3SFkLJWWgDvE44Ab3Ks5K/Qjt00xKmA2ulwgobE 3oCJvw82Q1StYXxNRakCJ3AeXJJhry+1Sibj8= Received: by 10.150.225.10 with SMTP id x10mr4364621ybg.207.1221153999011; Thu, 11 Sep 2008 10:26:39 -0700 (PDT) Received: by 10.65.35.4 with HTTP; Thu, 11 Sep 2008 10:26:38 -0700 (PDT) Message-ID: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> Date: Thu, 11 Sep 2008 22:56:38 +0530 From: "Mehul Chadha" To: freebsd-arch@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Adding Virtual kernel support to FreeBSD 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, 11 Sep 2008 17:55:58 -0000 hello all, We are a group of 3 students doing their graduation in computer science. We were thinking of implementing the virtual kernel support to freeBSD similar to what user mode linux does . We would be very thankful if we can have some suggestions and advice from your side. Thanks and Regards, Mehul From owner-freebsd-arch@FreeBSD.ORG Thu Sep 11 17:56:41 2008 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 3FB6D106566B for ; Thu, 11 Sep 2008 17:56:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id CB4F88FC15 for ; Thu, 11 Sep 2008 17:56:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8BHuVYO035323; Thu, 11 Sep 2008 13:56:32 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Matthew Dillon Date: Thu, 11 Sep 2008 10:28:59 -0400 User-Agent: KMail/1.9.7 References: <200809101531.54646.jhb@FreeBSD.org> <200809101806.38042.jhb@freebsd.org> <200809110006.m8B06vOU033199@apollo.backplane.com> In-Reply-To: <200809110006.m8B06vOU033199@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809111028.59610.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Thu, 11 Sep 2008 13:56:32 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8219/Thu Sep 11 11:02:39 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=4.2 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: arch@freebsd.org Subject: Re: PASSERT() - asserting for panics 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, 11 Sep 2008 17:56:41 -0000 On Wednesday 10 September 2008 08:06:57 pm Matthew Dillon wrote: > > :I think part of the pollution is that what I really want to do is treat a > :panic like an exception that I can catch. I could probably make that idiom > :work with two macros so your code can be: > : > : PANIC_TRY { > : /* do stuff */ > : } PANIC_CATCH("foo"); > : > :That could potentially work with some evil goto's that jumped between the > :macros (i.e. have the setjmp() in PANIC_CATCH and PANIC_TRY goto's down to > :-- > :John Baldwin > > Hmm. Almost java-like, where an exception pops back through subroutine > levels until it finds a match. That kind of functionality would be a > real mess in C. A limited form would be possible, something like this: > > #define PANIC_CATCH(label) \ (...) > static jmpbuf label # _jmpbuf > if (0) { > for (;;) { > longjmp(&label # _jmpbuf); > label: > > #define PANIC_RETRY }} > > #define PANIC_PANIC panic(...); }} > > #define PASSERT(label, cond) \ (...) > if (__predict_false(!(cond))) { > setjmp (&label # _jmpbuf); > goto label; > } > > PANIC_CATCH(badthings) { > ... > PANIC_RETRY; > } > > PANIC_CATCH(badthings) { > ... > PANIC_PANIC; > } > > PASSERT(badthings, x == 1); The problem is I want panics in unmodified code to be caught. For example, I want to write regression tests to make sure assertions on locking primivities fail when the state of the lock doesn't match what the assertion is requiring. I can do something fairly simple though that lets me do this: PANIC_TRY { stuff; } PANIC_CATCH { IGNORE_PANIC("this one is ok"); /* WITNESS can do different panics in foo_assert() sometimes */ IGNORE_PANIC("this one is too"); UNEXPECTED_PANIC(); } Without needing goto's. > Which would allow you some control over the context plus allow multiple > PASSERT's with the same label. But, OMG I don't know about doing > setjmp/longjmp in the kernel. I don't think it would be worth it. We use setjmp already if you get a trap in ddb so ddb doesn't crash. > Theoretically one could cross procedural boundaries with the longjmp, > and place the jmpbuf in a DATASET and have the kernel glue the longjmp > address. That would be a candidate for the C obfuscation contest > though. To catch unmodified panics, I have to have the longjmp in panic() itself, and I have the jmpbuf hung off of curthread. -- John Baldwin From owner-freebsd-arch@FreeBSD.ORG Thu Sep 11 18:18:15 2008 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 973F11065671 for ; Thu, 11 Sep 2008 18:18:15 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outt.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 851418FC1C for ; Thu, 11 Sep 2008 18:18:15 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id C63372416; Thu, 11 Sep 2008 11:03:24 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 73C0C2D6099; Thu, 11 Sep 2008 11:03:24 -0700 (PDT) Message-ID: <48C95D6D.80204@elischer.org> Date: Thu, 11 Sep 2008 11:03:25 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Mehul Chadha References: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> In-Reply-To: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Adding Virtual kernel support to FreeBSD 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, 11 Sep 2008 18:18:15 -0000 Mehul Chadha wrote: > hello all, > We are a group of 3 students doing their graduation in > computer science. We were thinking of implementing the virtual kernel > support to freeBSD similar to what user mode linux does . We would be very > thankful if we can have some suggestions and advice from your side. dragonflyBSD which is derived from freeBSD has this. > > Thanks and Regards, > Mehul > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-arch@FreeBSD.ORG Fri Sep 12 05:03:53 2008 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 8BC131065678 for ; Fri, 12 Sep 2008 05:03:53 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 788828FC0A for ; Fri, 12 Sep 2008 05:03:53 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id B1D781A3C37; Thu, 11 Sep 2008 22:03:52 -0700 (PDT) Date: Thu, 11 Sep 2008 22:03:52 -0700 From: Alfred Perlstein To: Julian Elischer Message-ID: <20080912050352.GB16977@elvis.mu.org> References: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> <48C95D6D.80204@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48C95D6D.80204@elischer.org> User-Agent: Mutt/1.4.2.3i Cc: Mehul Chadha , freebsd-arch@freebsd.org Subject: Re: Adding Virtual kernel support to FreeBSD 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, 12 Sep 2008 05:03:53 -0000 * Julian Elischer [080911 11:18] wrote: > Mehul Chadha wrote: > >hello all, > > We are a group of 3 students doing their graduation in > >computer science. We were thinking of implementing the virtual kernel > >support to freeBSD similar to what user mode linux does . We would be very > >thankful if we can have some suggestions and advice from your side. > > dragonflyBSD which is derived from freeBSD has this. Really??? :) What kind of porting effort would it take? -Alfred From owner-freebsd-arch@FreeBSD.ORG Fri Sep 12 05:44:39 2008 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 3201B1065676 for ; Fri, 12 Sep 2008 05:44:39 +0000 (UTC) (envelope-from mehulc87@gmail.com) Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by mx1.freebsd.org (Postfix) with ESMTP id C1D5D8FC18 for ; Fri, 12 Sep 2008 05:44:38 +0000 (UTC) (envelope-from mehulc87@gmail.com) Received: by gxk10 with SMTP id 10so18087801gxk.19 for ; Thu, 11 Sep 2008 22:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=mesPHG8JK7mWQa0LSWXZMfOaZ4zaSYd5k/v+fiJ6kCg=; b=i5EMGeVTQb75ck5BzSxDgbIlhwwpjBU7c4S82FQFsRWhFN74L2VXFCA557i6DFL41I 5DkBzzUw25VvfV1DWPtyI74tulvTY3X3m7DT/XbeWaE5XzgMro3YcH7YO9Bc93mVKvaI ZqN31vJeebS4F/TapzgXIEH49taIssuUCzBdQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=lmx4YOX8gbhsOOP8tWw7lHykeJm7NxXa3Vy4EFNv284ACNgJaf2GsPC/GQLJ+mmfs0 G02Pv7tZ8I5C4rAnyq6snCeBRszt8p4huRyFF4222g78Z2jGxegh9DabZJT+GtzLpCy0 Ip9vFLyJgBeF3eBHFgez/a3ZXKC4Nk7fO6FLg= Received: by 10.64.253.3 with SMTP id a3mr6096970qbi.40.1221198277551; Thu, 11 Sep 2008 22:44:37 -0700 (PDT) Received: by 10.65.35.4 with HTTP; Thu, 11 Sep 2008 22:44:37 -0700 (PDT) Message-ID: <251d650c0809112244w1995bc26r4f6622080034051d@mail.gmail.com> Date: Fri, 12 Sep 2008 11:14:37 +0530 From: "Mehul Chadha" To: "Alfred Perlstein" , "Julian Elischer" In-Reply-To: <20080912050352.GB16977@elvis.mu.org> MIME-Version: 1.0 References: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> <48C95D6D.80204@elischer.org> <20080912050352.GB16977@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-arch@freebsd.org Subject: Re: Adding Virtual kernel support to FreeBSD 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, 12 Sep 2008 05:44:39 -0000 A lot of effort to have a virtual kernel running on top of a real kernel. We will be dividing the project in a number of phases. We would be first concentrating on running the processes on virtual kernel (We are working for the algorithms), filesystems interface , next the libc interface that is the functions like printk in virtual kernel need to be mapped to printf of real kernel. Once we are through with this then we will start working with networks through the tun/tap interface . Any Thoughts?? On Fri, Sep 12, 2008 at 10:33 AM, Alfred Perlstein wrote: > * Julian Elischer [080911 11:18] wrote: > > Mehul Chadha wrote: > > >hello all, > > > We are a group of 3 students doing their graduation in > > >computer science. We were thinking of implementing the virtual kernel > > >support to freeBSD similar to what user mode linux does . We would be > very > > >thankful if we can have some suggestions and advice from your side. > > > > dragonflyBSD which is derived from freeBSD has this. > > Really??? :) > > What kind of porting effort would it take? > > -Alfred > From owner-freebsd-arch@FreeBSD.ORG Fri Sep 12 06:10:13 2008 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 2AB221065680 for ; Fri, 12 Sep 2008 06:10:13 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outB.internet-mail-service.net (outb.internet-mail-service.net [216.240.47.225]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB148FC27 for ; Fri, 12 Sep 2008 06:10:12 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id B4E5D2496; Thu, 11 Sep 2008 23:10:12 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 52E892D6024; Thu, 11 Sep 2008 23:10:12 -0700 (PDT) Message-ID: <48CA07C4.3040707@elischer.org> Date: Thu, 11 Sep 2008 23:10:12 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Alfred Perlstein References: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> <48C95D6D.80204@elischer.org> <20080912050352.GB16977@elvis.mu.org> In-Reply-To: <20080912050352.GB16977@elvis.mu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mehul Chadha , freebsd-arch@freebsd.org Subject: Re: Adding Virtual kernel support to FreeBSD 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, 12 Sep 2008 06:10:13 -0000 Alfred Perlstein wrote: > * Julian Elischer [080911 11:18] wrote: >> Mehul Chadha wrote: >>> hello all, >>> We are a group of 3 students doing their graduation in >>> computer science. We were thinking of implementing the virtual kernel >>> support to freeBSD similar to what user mode linux does . We would be very >>> thankful if we can have some suggestions and advice from your side. >> dragonflyBSD which is derived from freeBSD has this. > > Really??? :) > > What kind of porting effort would it take? matt says it would be doable.... > > -Alfred From owner-freebsd-arch@FreeBSD.ORG Fri Sep 12 06:15:29 2008 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 3C7E01065674 for ; Fri, 12 Sep 2008 06:15:29 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 1CAFD8FC27 for ; Fri, 12 Sep 2008 06:15:29 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id E3D1B23FA; Thu, 11 Sep 2008 23:15:28 -0700 (PDT) Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id 1DFEF2D601A; Thu, 11 Sep 2008 23:15:28 -0700 (PDT) Message-ID: <48CA0900.4030705@elischer.org> Date: Thu, 11 Sep 2008 23:15:28 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: Mehul Chadha References: <251d650c0809111026h1b16f5d2u77e8d611ce1b39f7@mail.gmail.com> <48C95D6D.80204@elischer.org> <20080912050352.GB16977@elvis.mu.org> <251d650c0809112244w1995bc26r4f6622080034051d@mail.gmail.com> In-Reply-To: <251d650c0809112244w1995bc26r4f6622080034051d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alfred Perlstein , freebsd-arch@freebsd.org Subject: Re: Adding Virtual kernel support to FreeBSD 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, 12 Sep 2008 06:15:29 -0000 Mehul Chadha wrote: > A lot of effort to have a virtual kernel running on top of a real kernel. > > We will be dividing the project in a number of phases. > > We would be first concentrating on running the processes on virtual > kernel (We are working for the algorithms), filesystems interface , next > the libc interface that is the functions like printk in virtual kernel > need to be mapped to printf of real kernel. Once we are through with > this then we will start working with networks through the tun/tap > interface . Any Thoughts?? > If dragonfly's vkernel support is now what you mean then what DO you mean? > On Fri, Sep 12, 2008 at 10:33 AM, Alfred Perlstein > wrote: > > * Julian Elischer > > [080911 11:18] wrote: > > Mehul Chadha wrote: > > >hello all, > > > We are a group of 3 students doing their > graduation in > > >computer science. We were thinking of implementing the virtual > kernel > > >support to freeBSD similar to what user mode linux does . We > would be very > > >thankful if we can have some suggestions and advice from your side. > > > > dragonflyBSD which is derived from freeBSD has this. > > Really??? :) > > What kind of porting effort would it take? > > -Alfred > > From owner-freebsd-arch@FreeBSD.ORG Fri Sep 12 18:27:24 2008 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 1B689106566B; Fri, 12 Sep 2008 18:27:24 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id D6FCC8FC29; Fri, 12 Sep 2008 18:27:23 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id D80D81CDCA; Fri, 12 Sep 2008 20:27:22 +0200 (CEST) Date: Fri, 12 Sep 2008 20:27:22 +0200 From: Ed Schouten To: FreeBSD FS , FreeBSD Arch Message-ID: <20080912182722.GK1191@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sU4rRG038CsJurvk" Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Mark van Cuijk , Jille Timmermans Subject: Expanding vops in vop_vectors during startup 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, 12 Sep 2008 18:27:24 -0000 --sU4rRG038CsJurvk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, Yesterday I was talking with some friends of mine about the FreeBSD VFS layer. As an exercise, Jille was trying to patch nullfs to hide .svn directories (see hackers@), so that's how we got to the subject. After talking about the way our vop_vector works (vop_bypass and vop_default), we were wondering why we don't propagate all pointers in the vop_vector to its children to save the unneeded function pointer resolving inside the VOP_* calls. I've created a patch that adds a new routine to the kernel, vop_vector_init(), which recursively expands the vops. A new macro (DECLARE_VOP_VECTOR) is used to automatically perform this when loading modules/booting. There is no need to reference default_vnodeops anymore, because it is now used implicitly (when vop_vector =3D=3D NULL). Any comments on the attached patch? I've only tested it with ufs, nullfs, devfs, etc. yet. I haven't tested `make universe' yet, but I suspect it shouldn't break hard. URL: http://80386.nl/files/vnode-vop-expand.diff Thanks! --=20 Ed Schouten WWW: http://80386.nl/ --sU4rRG038CsJurvk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkjKtIoACgkQ52SDGA2eCwWsoQCeLhN84yU86WavBhgGnSLrxXs5 pTMAnR5LoTV8qUpLi2FxO38Hr5pw0Tak =ALjF -----END PGP SIGNATURE----- --sU4rRG038CsJurvk--