From owner-freebsd-arch@freebsd.org Sun Jun 24 09:51:39 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7B9410219F1 for ; Sun, 24 Jun 2018 09:51:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 453CF820CE for ; Sun, 24 Jun 2018 09:51:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0936910219F0; Sun, 24 Jun 2018 09:51:39 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAF1110219EF for ; Sun, 24 Jun 2018 09:51:38 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 901D7820CA for ; Sun, 24 Jun 2018 09:51:38 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x230.google.com with SMTP id g123-v6so3475627ywf.13 for ; Sun, 24 Jun 2018 02:51:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to; bh=LjRHJ/U6CENyQaTSWd6xvSxXNF2zje3weGwXcU9LUeY=; b=Aq+UJ1lwUIi2v67WcC+ZVGXBiSv7dfNNBzhaTUY0YBTALAiH0IkwO+E3FQZ6B+QvK5 PMhKTS4C1TDOWWclsswBkkLGyuY7ic1R0FgSqexSfFjlNn8xFu6NIO/otKKvei2/QdEY ZMmIqve9y05tJIFAzpcVf+bwXxmQe1lFFsNNE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LjRHJ/U6CENyQaTSWd6xvSxXNF2zje3weGwXcU9LUeY=; b=tnVI4oRPrOvzCzFbKk/PTmZ/rm+YYgFUQJ02mgIXqRITx79Q7yKldxDY8a7lln4XSa iLa6laM3Lo+bn11A0qcUOUSNwYhhs8rcn7wJn/bAiYL5yDbX5GvzyT2IDpXR2RYyQ5V7 gitjm40FNJqPE7xPUO5HvkhAOc8/mRpIpzCjPJFjpkW06qsAYQtQoKiqE0S/fNnvO7BA bt3Rb/M2CivSW+WXxbRvz2YeGycS3uln6vT244jhqvs1x0WLHl5DNKE3cFDqlOJCy68Y E1tzPz+wSpuMDNU56MirBQ5O92egF+/h8oMHzN4HkyCmUULktwT9fdup+x+1ZPL5ZMtR plLA== X-Gm-Message-State: APt69E1tLursnCyeQrDVBtb7u8W8HxJfoNaK/rM6ZZMyU9Cxe8dxZLhL kMyt6J+htDWX13yYQnJVDSd4RpbWMo7veIa8HgOrsg== X-Google-Smtp-Source: AAOMgpfhTUWG9hnRBgpHsET1psWzWcxsK/KEuze5uhmlqbqdYZm9j8OQhg1Fahhj6MyMrHYmkpuA6ZnyoDd4zAcUwGY= X-Received: by 2002:a0d:f843:: with SMTP id i64-v6mr256937ywf.182.1529833897592; Sun, 24 Jun 2018 02:51:37 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 02:51:06 -0700 (PDT) From: Eitan Adler Date: Sun, 24 Jun 2018 02:51:06 -0700 Message-ID: Subject: xstr, mkstr To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 09:51:39 -0000 Why are these tools in base? As far as I could tell these tools are un-used in the build process and otherwise specialized tools. Is there any reason we still have them in the toolchain or in base? -- Eitan Adler From owner-freebsd-arch@freebsd.org Sun Jun 24 10:39:56 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDDCE10234DE for ; Sun, 24 Jun 2018 10:39:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7DABE8399D for ; Sun, 24 Jun 2018 10:39:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3733D10234DD; Sun, 24 Jun 2018 10:39:55 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 244E610234DC for ; Sun, 24 Jun 2018 10:39:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACBD18399C for ; Sun, 24 Jun 2018 10:39:54 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22c.google.com with SMTP id s14-v6so4113382ybp.13 for ; Sun, 24 Jun 2018 03:39:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=F7X2sd4eRk7B4alRI3V0ZDUQ47Vi2m20Oje8rNwTOJc=; b=q5azbO2H3LktqPCVCl94ZG8At7xdfuJiGU6efpNhfATk3l+xqhhw55Brde561fVafx qVMNvtfXUctoSGc6TBJ+5dZ/UpSzi+2waGpp5Yo3/wEnYhsooHqhbU6V33Ug5ZkMa15Y 8kTzAEuZ29EEiuTyh4ueT17ovIodixQEh5nGU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=F7X2sd4eRk7B4alRI3V0ZDUQ47Vi2m20Oje8rNwTOJc=; b=PW1y/p85xEVXFqwmopM4wseNmfPSL9GQ6K1/3nAFK4Fzy6S13TxmwHKGZ2llyneVew oDBkEic6moZAE2m2Nji3L1i/EHBAEpFD/Uw8IBZaJWVxmnaJ0EWdQaTJh/lDjHJnuQMP 8r/8fZoZoCFzRL73bvHutsQzNRezaVI1zdxwZ+gBSn0LU3KP0qMm46FXR5lXDUtPJYjI WdN6RXjEPkDCe0uVoYgSunxWJ+IpR4Oth1WKt4V1laLGghgnQ3NZgiTqPUSvM0aZNbfL F1+2IksDRhbsNa/8unOGHG4E0rhKMgvRPupB1i/rai5VkN2HNXjYm+4iwMVz73WtIyJf cGaA== X-Gm-Message-State: APt69E2W3q493yd6+ObBI+H6YPily2HXgTDpZ1C9fNgVVkvdXj37NMQP 1+pXBldPgefy4P8LKHVo8MNz8LeTf4Y0PjsyCfkTrA== X-Google-Smtp-Source: ADUXVKI+ugPbsfQnkK6SgjM1pVxVejmvW8rLqOzy8IG4dFpUpOf1hutRubjoVLNBoZ/HSeE4zN0GM+q1o3x3NojiF6o= X-Received: by 2002:a25:786:: with SMTP id 128-v6mr4331723ybh.338.1529836793843; Sun, 24 Jun 2018 03:39:53 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 03:39:23 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Sun, 24 Jun 2018 03:39:23 -0700 Message-ID: Subject: Re: What to do about rcmdsh(3) ? To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 10:39:56 -0000 On 24 June 2018 at 03:32, Eitan Adler wrote: > Now that the rcmds are removed from base, it opens a question about > what to do with rcmdsh(3). > This is documented as > rcmdsh =E2=80=93 return a stream to a remote command without superus= er > And is implemented as a rather simple wrapper of getaddrinfo and exec. > > This isn't something I'd imagine we'd add to libc now-a-days and is > currently broken by default (due to defaulting to _PATH_RSH) > > I'm not sure there is much value in keeping this function around. I > did a rather naive search for uses of this function in ports and > couldn't find any. I'm preparing a more comprehensive patch for an > exp-run. > > Does anyone have a reason to keep in libc? Any objection to removing > it? If no, is there anything special I need to do beyond just removing > the implementation and references? Since I'm sending emails at 3:30am anyways, I'll point that generally applies to rcmd(3) and related too. I don't really understand the use-case for these functions on modern system= s. --=20 Eitan Adler From owner-freebsd-arch@freebsd.org Sun Jun 24 10:32:46 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD7DE10231B9 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6563B83844 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2771210231B7; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1512B10231B6 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD63783842 for ; Sun, 24 Jun 2018 10:32:45 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x235.google.com with SMTP id s14-v6so4110549ybp.13 for ; Sun, 24 Jun 2018 03:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=gFxC4TTdkWXENkiFjpeZmug2cweTMUojdYoxiwL00pM=; b=lbI5Y2pIB42rcaa4OXidkHZryfu0h9VmGkgbF6pQFm2G/jBNuucqFLr4ILP1YhsPc3 PjjXp/iq3jS/Lo+B21A6+r2VYs+qne/EruP9FuFMCNTTrYY6JQwOEb8+mLgPOqSJj6/j TFfxhlJM9WM/b6Wy1B1B1sMn5P+8L3OGwDgQE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=gFxC4TTdkWXENkiFjpeZmug2cweTMUojdYoxiwL00pM=; b=rvtYthR5kHx2shbCtVsOXKNys0PqWCTrzNntB9teRx6faOoh2CjPTyEVd4mWsCN+F0 IcD32GW02ED6BFGRU0tpTi+mOENFhO5/4H/6rTce2qkXjO70qAHxBCHiY7LMDvM0XYdQ 6S+Z9d98mgDtotDOityygUCYBrYHYeXc1kE5q0hwjmwv7RX9uA7YyVGL7CIHBR2R9eQc EP80P7GOmhjHF3NtQDVtMv+ryecFsw4TFUlRftBbupu1gn617ABtTjeoXw9dr1wBQfjP Kcvy9KSrddp0gVShoB0fHml8/GsGaFcaFyAWtNSVqGLbGTU9CGDyQ6ogSsdjaPS3fZMO bcgg== X-Gm-Message-State: APt69E3uJ5Sks1PP9riH3bErf7teft9D6sDCguVpPXC+VdgGaPNA/Q89 28YlxcmhoBEH/S4LRcKT+JN3C1LSs/CPJ/qo53O9Wgkj X-Google-Smtp-Source: ADUXVKKogjN/W4KM0FAyOD5VWQJZg6m/hBFkErnSB0farnCqNaOPdTMWcMYWLfapKc2nbXkjM+tYs0NASK+dEJIzAMU= X-Received: by 2002:a25:734f:: with SMTP id o76-v6mr3984480ybc.69.1529836364814; Sun, 24 Jun 2018 03:32:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 03:32:13 -0700 (PDT) From: Eitan Adler Date: Sun, 24 Jun 2018 03:32:13 -0700 Message-ID: Subject: What to do about rcmdsh(3) ? To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 10:32:47 -0000 Now that the rcmds are removed from base, it opens a question about what to do with rcmdsh(3). This is documented as rcmdsh =E2=80=93 return a stream to a remote command without superuser And is implemented as a rather simple wrapper of getaddrinfo and exec. This isn't something I'd imagine we'd add to libc now-a-days and is currently broken by default (due to defaulting to _PATH_RSH) I'm not sure there is much value in keeping this function around. I did a rather naive search for uses of this function in ports and couldn't find any. I'm preparing a more comprehensive patch for an exp-run. Does anyone have a reason to keep in libc? Any objection to removing it? If no, is there anything special I need to do beyond just removing the implementation and references? --=20 Eitan Adler From owner-freebsd-arch@freebsd.org Sun Jun 24 12:14:25 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B46BA102740F for ; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4E26B87017 for ; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 078BF102740E; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8F68102740D for ; Sun, 24 Jun 2018 12:14:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A1F187016 for ; Sun, 24 Jun 2018 12:14:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5OCECHU074062; Sun, 24 Jun 2018 15:14:15 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5OCECHU074062 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5OCECGl074061; Sun, 24 Jun 2018 15:14:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 24 Jun 2018 15:14:12 +0300 From: Konstantin Belousov To: Eitan Adler Cc: "freebsd-arch@freebsd.org" Subject: Re: What to do about rcmdsh(3) ? Message-ID: <20180624121412.GY2430@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 12:14:25 -0000 On Sun, Jun 24, 2018 at 03:32:13AM -0700, Eitan Adler wrote: > Now that the rcmds are removed from base, it opens a question about > what to do with rcmdsh(3). > This is documented as > rcmdsh ??? return a stream to a remote command without superuser > And is implemented as a rather simple wrapper of getaddrinfo and exec. > > This isn't something I'd imagine we'd add to libc now-a-days and is > currently broken by default (due to defaulting to _PATH_RSH) > > I'm not sure there is much value in keeping this function around. I > did a rather naive search for uses of this function in ports and > couldn't find any. I'm preparing a more comprehensive patch for an > exp-run. There is a huge value in keeping ABI compatibility. The symbol must be kept. You may remove default version for the symbol if you are so inclined. > > Does anyone have a reason to keep in libc? Any objection to removing > it? If no, is there anything special I need to do beyond just removing > the implementation and references? > > -- > Eitan Adler > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" From owner-freebsd-arch@freebsd.org Mon Jun 25 09:01:38 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 093851002870 for ; Mon, 25 Jun 2018 09:01:38 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9A6D67330D for ; Mon, 25 Jun 2018 09:01:37 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 59556100286D; Mon, 25 Jun 2018 09:01:37 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46E6F100286C for ; Mon, 25 Jun 2018 09:01:37 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id D724873306 for ; Mon, 25 Jun 2018 09:01:36 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id EAA5314857; Mon, 25 Jun 2018 09:01:35 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5P91Z14019343 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Jun 2018 09:01:35 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5P91ZVO019342; Mon, 25 Jun 2018 09:01:35 GMT (envelope-from phk) To: Warner Losh cc: "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC In-reply-to: From: "Poul-Henning Kamp" References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19340.1529917294.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jun 2018 09:01:34 +0000 Message-ID: <19341.1529917294@critter.freebsd.dk> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 09:01:38 -0000 -------- In message , Warner Losh writes: >So here's my open questions: >(1) Do I need to parse boot.conf? I can't see how it would add any value on top of UEFI and reading it will just keeping old workarounds alive another decade for no good reason. -- = 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 Mon Jun 25 09:18:58 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D9671002F27 for ; Mon, 25 Jun 2018 09:18:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DE3A073B1D for ; Mon, 25 Jun 2018 09:18:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9BCDA1002F26; Mon, 25 Jun 2018 09:18:57 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A12C1002F24 for ; Mon, 25 Jun 2018 09:18:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 007C873B1B for ; Mon, 25 Jun 2018 09:18:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5P9IiG6059602; Mon, 25 Jun 2018 12:18:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5P9IiG6059602 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5P9IiZ4059601; Mon, 25 Jun 2018 12:18:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Jun 2018 12:18:44 +0300 From: Konstantin Belousov To: Poul-Henning Kamp Cc: Warner Losh , "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC Message-ID: <20180625091844.GC2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19341.1529917294@critter.freebsd.dk> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 09:18:58 -0000 On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > -------- > In message > , Warner Losh writes: > > >So here's my open questions: > >(1) Do I need to parse boot.conf? > > I can't see how it would add any value on top of UEFI and reading it > will just keeping old workarounds alive another decade for no good reason. An obvious values is to have serial console earlier than loader.conf is parsed. At least on typical desktop motherboards which do not have serial bios redirection, this is important. From owner-freebsd-arch@freebsd.org Mon Jun 25 13:37:22 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E77AF100F27D for ; Mon, 25 Jun 2018 13:37:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7C8A27CC05 for ; Mon, 25 Jun 2018 13:37:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 329D2100F278; Mon, 25 Jun 2018 13:37:21 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA205100F277 for ; Mon, 25 Jun 2018 13:37:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8724C7CC04 for ; Mon, 25 Jun 2018 13:37:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22c.google.com with SMTP id v83-v6so12369015itc.3 for ; Mon, 25 Jun 2018 06:37:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=K8viVGdRufGl7zXPb1hyMqBnlmjoEAROpIn0bJBpJ3w=; b=bsedDp15oLa47q0ukczZJqaobdWju1VvRKj3fmvuDqM7WI/ZO18fquHQbMm8ryy6ch jnBD5WebQJfLyo4IZrP/EB2GkALPUNgo2JpJ4XOXVlp70IZt5DsO1SjQ3e1+Vq8tsEJa Wgqz8SOUazeet26ydha8UYO9S5Dx8lnbEF6hAvO36I0CXiCuM2Z7nDaua34iElBjT0AB 31oTU+gohl+xx11u3GUoYr87MS63toRz2h7Gp96L7Kz3kVLi0RadTYMFeT/NhvsUHBJg zuhPj+XtkSh3ZncjIZzT5yEiSpFollaetLcwfjhcpSixk3kG/oiNWWmHpjRRMG1UvYyL r7hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=K8viVGdRufGl7zXPb1hyMqBnlmjoEAROpIn0bJBpJ3w=; b=narZS2O6UOROD+11cU71S2Uwh0H8m96ptWGlW4CqLSCSnoYgfglYBgCNApVyLvSGV/ H+Xl9An/w+TjqgAjmZng2qKrfdTBp0suNZfjRBrL+3O6x2375HOCuwxlh6MooO7WVAgU 3uhU+MEsAilgMLgIBemW1vFEdIU/zTACFosNywjTpLBHWRrpt4o/T0YwJ4O7VEsvVQ1D 0yGrRjs3CatwMUMRCtgI5pBFmhNPjDWzWooteeKnR6cn2MP+pTlWD3BslxRWNyjaBM8T 9JvqRBuGK7+PtOcpnF7989t53bEH3x+e8pxxMr10oBF8kxwm4eHSGeVN+73r3HUx1UWz R6Yg== X-Gm-Message-State: APt69E01MIsruHEwTjRapatgD9TQzxR0tqIqpeW2PyWKMF5nFA4qlcMn efIqpM9X9n2RoPObz9WobSTrgUeL1biFYOkifcbi1w== X-Google-Smtp-Source: ADUXVKL8dGkfyj3dGn2d5zuHOrX0vpp0mIguQ1D5IUt3nkz426vbXDENyeF0omgK+Pj7dfAzY5jWAa+UypTk+HrpW2E= X-Received: by 2002:a24:7c8d:: with SMTP id a135-v6mr920448itd.73.1529933839766; Mon, 25 Jun 2018 06:37:19 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 06:37:19 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20180625091844.GC2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> From: Warner Losh Date: Mon, 25 Jun 2018 07:37:19 -0600 X-Google-Sender-Auth: Q90uG3lyB7TU-s2_-UBvgmpfm14 Message-ID: Subject: Re: UEFI Plans / Shifts -- RFC To: Konstantin Belousov Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 13:37:22 -0000 On Mon, Jun 25, 2018 at 3:18 AM, Konstantin Belousov wrote: > On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > > -------- > > In message gmail.com> > > , Warner Losh writes: > > > > >So here's my open questions: > > >(1) Do I need to parse boot.conf? > > > > I can't see how it would add any value on top of UEFI and reading it > > will just keeping old workarounds alive another decade for no good > reason. > > An obvious values is to have serial console earlier than loader.conf is > parsed. At least on typical desktop motherboards which do not have > serial bios redirection, this is important. > This won't work until AFTER we add ACPI to the boot loader. Warner From owner-freebsd-arch@freebsd.org Mon Jun 25 15:47:53 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C73910142FD for ; Mon, 25 Jun 2018 15:47:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3719D826EB for ; Mon, 25 Jun 2018 15:47:53 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EBAEA10142FC; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9F1310142FB for ; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57DC7826EA for ; Mon, 25 Jun 2018 15:47:52 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5PFlelU048986; Mon, 25 Jun 2018 18:47:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5PFlelU048986 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5PFleEw048985; Mon, 25 Jun 2018 18:47:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Jun 2018 18:47:40 +0300 From: Konstantin Belousov To: Warner Losh Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC Message-ID: <20180625154740.GF2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 15:47:53 -0000 On Mon, Jun 25, 2018 at 07:37:19AM -0600, Warner Losh wrote: > On Mon, Jun 25, 2018 at 3:18 AM, Konstantin Belousov > wrote: > > > On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > > > -------- > > > In message > gmail.com> > > > , Warner Losh writes: > > > > > > >So here's my open questions: > > > >(1) Do I need to parse boot.conf? > > > > > > I can't see how it would add any value on top of UEFI and reading it > > > will just keeping old workarounds alive another decade for no good > > reason. > > > > An obvious values is to have serial console earlier than loader.conf is > > parsed. At least on typical desktop motherboards which do not have > > serial bios redirection, this is important. > > > > This won't work until AFTER we add ACPI to the boot loader. Why ? From owner-freebsd-arch@freebsd.org Mon Jun 25 17:25:57 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDED61017BCD for ; Mon, 25 Jun 2018 17:25:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 424C885BD3 for ; Mon, 25 Jun 2018 17:25:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id F34F71017BCB; Mon, 25 Jun 2018 17:25:55 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD4841017BCA for ; Mon, 25 Jun 2018 17:25:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D18F85BD2 for ; Mon, 25 Jun 2018 17:25:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id e15-v6so13304647iog.1 for ; Mon, 25 Jun 2018 10:25:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=xj9/2JkTuE4EpF3Q2WDqvomueS9YnI25gr53RnZpow4=; b=IZrmrungcYfyAcMugz88aRGgr7ibS0+jsJ1IeoIqtw0ZsGfoE4Zn8Kt+IuI7Jg3za2 p78WG7IeYxQ95BGx+hdFhS7TyGCt6gQIzXHZQVUJdSehX8EsP2uJs8k4gUVD9e0cTX2/ wSCztsYKepHeQt8Trlg4Wo5J5M6+vOENtBZOh9MBONyQX2Vc9sxubUuGPQIdQJ24NBkg m15/aDfgvtDjrdTNxhLeRpzo00WjBHC/C+zNB/O9XKKU1UgWBl4dCDLbJDot53mT41qd 3PhaIvo1/4u04QUcgckZ0fSgJrp52gY12zTKKD2nLnEi+ga3ur+b7wNi9xX+Naf2WzoD 8OYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xj9/2JkTuE4EpF3Q2WDqvomueS9YnI25gr53RnZpow4=; b=W5c3HjBCKPCmrHpmbQ720yLdFZlJvGGB9oF0oQYcOT18DAd9cIFLKQzdwTeETme1fq ND216U1Hf15dB2QBbZJjOGnl6x/vUJx1oCNgeo4wwWZDzJTpSI6+J0uMxbdgFIg2AJ8Z LJwU0wVHwGljqbnksP5yACNzXEQoBvASuKk+KnZso6viKzs3WCJUC8zgcpn98KyEWQtA ASbFk4kILjtbZFz9wVkZFWLDaz0DYzFa9h4ayGAPb2x/cvFcgKrQsFu0xDi5YZ9DSlzw YhDP9/ivIG4PwfHn29cPmdzw4uk/YRpqxN7+B9i6UklbvwSkcc6jiy3WzCFCnktB1e9d I0LA== X-Gm-Message-State: APt69E2ZpgLyporr/qxLEOXuzZxL6YXYXB4jgshl8mxsEgW1jCkkO14Y UnIFR9CjZMu6Wr67vbgHyvqpRSVi49uxIfi1yJxXjA== X-Google-Smtp-Source: AAOMgpflXMG9wjXL2W90VB+BdX0EJhJ+saKFfsCDUOi5rnjDxInUYaMXVCidEdTaNQPsCpwSjflyxDl03xbCiZNgNN4= X-Received: by 2002:a6b:280a:: with SMTP id o10-v6mr1801804ioo.168.1529947554496; Mon, 25 Jun 2018 10:25:54 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 10:25:53 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: <20180625154740.GF2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> <20180625154740.GF2430@kib.kiev.ua> From: Warner Losh Date: Mon, 25 Jun 2018 11:25:53 -0600 X-Google-Sender-Auth: onBU_WPneEHxx_c7r0lIZW5Zseo Message-ID: Subject: Re: UEFI Plans / Shifts -- RFC To: Konstantin Belousov Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 17:25:57 -0000 On Mon, Jun 25, 2018 at 9:47 AM, Konstantin Belousov wrote: > On Mon, Jun 25, 2018 at 07:37:19AM -0600, Warner Losh wrote: > > On Mon, Jun 25, 2018 at 3:18 AM, Konstantin Belousov < > kostikbel@gmail.com> > > wrote: > > > > > On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > > > > -------- > > > > In message xsHQjX31zOo+8mDwMAQuA@mail. > > > gmail.com> > > > > , Warner Losh writes: > > > > > > > > >So here's my open questions: > > > > >(1) Do I need to parse boot.conf? > > > > > > > > I can't see how it would add any value on top of UEFI and reading it > > > > will just keeping old workarounds alive another decade for no good > > > reason. > > > > > > An obvious values is to have serial console earlier than loader.conf is > > > parsed. At least on typical desktop motherboards which do not have > > > serial bios redirection, this is important. > > > > > > > This won't work until AFTER we add ACPI to the boot loader. > > Why ? > Because often (very often in my experience) the redirected serial port is not at COM1 address, but COM2 or COM3. The only way to set that is via comconsole_port. That's not parsed until after we read in loader.conf when we kick the different language interpreters off. So, any output before that will be lost. This happens when we call interact, which is after all the initial boot stuff has happened. The UEFI boot variable ConOut gives us a device which rendered to human readable form looks something like: PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/PciRoot(0x0)/Pci(0x1f,0x0)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenVt100Plus() which tells us a lot. There's two devices. First one listed is a video card whose ACPI _ADR is 0x80010100. The second one is the Serial Port with _UID=1 running at 115200 baud and that supports Vt100-ish escape sequences. What the boot loader doesn't know is what the port address of UID=1 is with any certainty. On my specific system, it maps to: uart1 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPC0.UAR2 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 which is actually COM2. Now, there's some text in the ACPI standard that says suggests that _UID=0 should be COM1, 1 COM2 etc, but it appears to be mostly a suggestion not an absolute requirement. The only requirement is that _UID=X is the same from boot to boot. I'd thought about putting in some fallback code for this, but a sampling of systems suggests this might be a bit optimistic. Here's a sampling of a couple of systems I have: Supermicro X11 based: uart0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PC00.LPC0.UAR1 uart2 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PC00.LPC0.UAR2 Supermicro X10 based: uart0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC0.UAR1 uart1 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPC0.UAR2 Supermicro X9 based: uart0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPCB.UAR1 unknown pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.LPCB.UAR2 (disabled) uart2 pnpinfo _HID=PNP0501 _UID=3 at handle=\_SB_.PCI0.LPCB.UAR3 Freefall: uart0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPCB.UAR1 uart1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.LPCB.UAR2 uart2 pnpinfo _HID=PNP0501 _UID=3 at handle=\_SB_.PCI0.LPCB.UR12 So UID=1 could mean COM1, COM2 or COM3, and that's just on SuperMicro hardware from the last few years.... Adding ACPI (to the UEFI-only boot loader, nothing else) would allow us to go search the UEFI tree for the PNP0501 node with the right _UID. It's kinda a heavy lift though. I thought about adding something that would set a FreeBSD-specific env var that would give the loader.efi a hint to make things work on the second boot (the first boot setting it in rc.d somewhere). But that's a fragile solution at best, and wouldn't solve the serial installer issues. Warner From owner-freebsd-arch@freebsd.org Mon Jun 25 17:40:49 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4291F1018348 for ; Mon, 25 Jun 2018 17:40:49 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CE1D086373 for ; Mon, 25 Jun 2018 17:40:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 8B9791018347; Mon, 25 Jun 2018 17:40:48 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 794971018346 for ; Mon, 25 Jun 2018 17:40:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 0F83886371 for ; Mon, 25 Jun 2018 17:40:48 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 01CBD14858; Mon, 25 Jun 2018 17:40:46 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5PHekLS020856 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Jun 2018 17:40:46 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5PHejoN020855; Mon, 25 Jun 2018 17:40:45 GMT (envelope-from phk) To: Warner Losh cc: Konstantin Belousov , "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC In-reply-to: From: "Poul-Henning Kamp" References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> <20180625154740.GF2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20853.1529948445.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jun 2018 17:40:45 +0000 Message-ID: <20854.1529948445@critter.freebsd.dk> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 17:40:49 -0000 -------- In message , Warner Losh writes: >I thought about adding something that would set a FreeBSD-specific env va= r >that would give the loader.efi a hint to make things work on the second >boot (the first boot setting it in rc.d somewhere). But that's a fragile >solution at best, and wouldn't solve the serial installer issues. In the very special case of the installer, how hard would it be to give loader.efi a compiletime option of "All serial ports and video" ? -- = 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 Mon Jun 25 18:25:39 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECB5B101A3AA for ; Mon, 25 Jun 2018 18:25:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7932188532 for ; Mon, 25 Jun 2018 18:25:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 350AE101A3A9; Mon, 25 Jun 2018 18:25:38 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12959101A3A8 for ; Mon, 25 Jun 2018 18:25:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 984BE88530 for ; Mon, 25 Jun 2018 18:25:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id j135-v6so13758950itj.1 for ; Mon, 25 Jun 2018 11:25:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zzX9jhIprPl0e+oaD8ipuvVKoRe6+vIIY5KfM579qe0=; b=mHcfHtfLvBSzm6TXiZm4M+Xe5LkSQcyTIBSgRjXXSukTzTjsFfRFHoLe9kdjcVXs6e s6O2rWuwtwXeIUHY+8sBfhXYwjtA/jVdMbl6WfCB8V3rL47NNr16vPE7A5x3c/MKQpT1 HSpx2+M/l1mMBwn1ITPAv85BSr6977og22vSnqLzQIsnYCzVET1KCNnw9M7x1/vshmhc dD9ss6vW5HjJeYlI5T06MzhJ3RopNVRtNvEE8Z/JK6JfsyAJhABnL6B1W21isX+u8GMV OHv6/0nhurMHLviOHE8TqACm0g/iNJeSgScGRZ7EBLGXG8jch9WnS9pBVrst7oHti+jo 1Isg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zzX9jhIprPl0e+oaD8ipuvVKoRe6+vIIY5KfM579qe0=; b=meYPLiRQl9FIpTleKfMea1NfShKkNvD4BH9zJQ8KX3JaLdnS+I/KjK2XTsfMDRgFRh hceJDjfDmdEA5X9MLwVimOWvEAagch1YQCXrzi3GXIaOqKrlR1Re+gYleWiszFJL2KHo vaIggIVdgBTprb0wS8hi+lWMACDGJN7NHmqx3g12ZO/lpMcnmE9EvRmAHSQ8UkGi3E9s 7uLbed1sN+uvcCqu+hiHmeW8hANWNCyySr1FNL0DzMVJVV6Fx9OZouTCZk2Z6Qc2ht5l hgMfn9XHqNj67Qy0+mCvWB8SfVGFqeWt+ckP6YXz2wLKXsCFt2HB1zjgzqGa7O9o6Yay J6Kw== X-Gm-Message-State: APt69E3Z3N14T8hh3/Cw7uaTLIjSQ6QfoAtlECsh4ZSknBRMetfnhT+h bV0J6zlPkTL/TLbDlc9RLWxiGK2iokM3xx5iAR0R8g== X-Google-Smtp-Source: AAOMgpdnLlJYRpNUdQcJjH3TvciCnmPzgpXqPkASwEO+CXm0FP7LSvDBk5IdGW4ah9/HB6z6SXiUNcMSeI/Ab4VRa4g= X-Received: by 2002:a24:64ce:: with SMTP id t197-v6mr1844891itc.36.1529951136749; Mon, 25 Jun 2018 11:25:36 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Mon, 25 Jun 2018 11:25:36 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: <20854.1529948445@critter.freebsd.dk> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> <20180625154740.GF2430@kib.kiev.ua> <20854.1529948445@critter.freebsd.dk> From: Warner Losh Date: Mon, 25 Jun 2018 12:25:36 -0600 X-Google-Sender-Auth: G0IC4xX2nPpW5r463IYQ91IvtDk Message-ID: Subject: Re: UEFI Plans / Shifts -- RFC To: Poul-Henning Kamp Cc: Konstantin Belousov , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 18:25:39 -0000 On Mon, Jun 25, 2018 at 11:40 AM, Poul-Henning Kamp wrote: > -------- > In message gmail.com> > , Warner Losh writes: > > >I thought about adding something that would set a FreeBSD-specific env var > >that would give the loader.efi a hint to make things work on the second > >boot (the first boot setting it in rc.d somewhere). But that's a fragile > >solution at best, and wouldn't solve the serial installer issues. > > In the very special case of the installer, how hard would it be to > give loader.efi a compiletime option of "All serial ports and video" ? There's much diversity here. There's 4 choices at standard addresses, plus PCI options and a few non-standard choices (though some of those are really PCI). And people often connect other things to their serial ports, so blasting all of them may be unwise if you have a 'sealed box' that you then do a serial install on. Is it possible? Sure. I'm just not sure it's wise. We tried something similar recently with the GELI boot blocks and it broke a lot of people. Warner From owner-freebsd-arch@freebsd.org Mon Jun 25 20:49:28 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D2B2101ED1A for ; Mon, 25 Jun 2018 20:49:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F12658CFEF for ; Mon, 25 Jun 2018 20:49:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B17B1101ED17; Mon, 25 Jun 2018 20:49:27 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D494101ED15 for ; Mon, 25 Jun 2018 20:49:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14AF48CFEE for ; Mon, 25 Jun 2018 20:49:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5PKnBS3018510; Mon, 25 Jun 2018 23:49:14 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5PKnBS3018510 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5PKnAY6018509; Mon, 25 Jun 2018 23:49:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 25 Jun 2018 23:49:10 +0300 From: Konstantin Belousov To: Warner Losh Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" Subject: Re: UEFI Plans / Shifts -- RFC Message-ID: <20180625204910.GG2430@kib.kiev.ua> References: <19341.1529917294@critter.freebsd.dk> <20180625091844.GC2430@kib.kiev.ua> <20180625154740.GF2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 20:49:28 -0000 On Mon, Jun 25, 2018 at 11:25:53AM -0600, Warner Losh wrote: > On Mon, Jun 25, 2018 at 9:47 AM, Konstantin Belousov > wrote: > > > On Mon, Jun 25, 2018 at 07:37:19AM -0600, Warner Losh wrote: > > > On Mon, Jun 25, 2018 at 3:18 AM, Konstantin Belousov < > > kostikbel@gmail.com> > > > wrote: > > > > > > > On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > > > > > -------- > > > > > In message > xsHQjX31zOo+8mDwMAQuA@mail. > > > > gmail.com> > > > > > , Warner Losh writes: > > > > > > > > > > >So here's my open questions: > > > > > >(1) Do I need to parse boot.conf? > > > > > > > > > > I can't see how it would add any value on top of UEFI and reading it > > > > > will just keeping old workarounds alive another decade for no good > > > > reason. > > > > > > > > An obvious values is to have serial console earlier than loader.conf is > > > > parsed. At least on typical desktop motherboards which do not have > > > > serial bios redirection, this is important. > > > > > > > > > > This won't work until AFTER we add ACPI to the boot loader. > > > > Why ? > > > > Because often (very often in my experience) the redirected serial port is > not at COM1 address, but COM2 or COM3. The only way to set that is via > comconsole_port. That's not parsed until after we read in loader.conf when > we kick the different language interpreters off. So, any output before that > will be lost. This happens when we call interact, which is after all the > initial boot stuff has happened. Machines which have BIOS redirection usually double the output to the video device (framebuffer or vga), and to the serial, exactly as you note in the decoding of the sample below. On the other hand, desktop-class boards almost never have either serial redirection nor the double-output, only have one serial port (COM1) and this is where the early switch to the serial is most useful. It is fine to only support ISA COM1 for that. > > The UEFI boot variable ConOut gives us a device which rendered to human > readable form looks something like: > PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/Pci(0x0,0x0)/AcpiAdr(0x80010100),/PciRoot(0x0)/Pci(0x1f,0x0)/Serial(0x1)/Uart(115200,8,N,1)/UartFlowCtrl(Hardware)/VenVt100Plus() > > which tells us a lot. There's two devices. First one listed is a video card > whose ACPI _ADR is 0x80010100. The second one is the Serial Port with > _UID=1 running at 115200 baud and that supports Vt100-ish escape sequences. > What the boot loader doesn't know is what the port address of UID=1 is with > any certainty. On my specific system, it maps to: > uart1 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPC0.UAR2 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > which is actually COM2. Now, there's some text in the ACPI standard that > says suggests that _UID=0 should be COM1, 1 COM2 etc, but it appears to be > mostly a suggestion not an absolute requirement. The only requirement is > that _UID=X is the same from boot to boot. I'd thought about putting in > some fallback code for this, but a sampling of systems suggests this might > be a bit optimistic. Here's a sampling of a couple of systems I have: > > Supermicro X11 based: > uart0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PC00.LPC0.UAR1 > uart2 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PC00.LPC0.UAR2 > Supermicro X10 based: > uart0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC0.UAR1 > uart1 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPC0.UAR2 > Supermicro X9 based: > uart0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPCB.UAR1 > unknown pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.LPCB.UAR2 > (disabled) > uart2 pnpinfo _HID=PNP0501 _UID=3 at handle=\_SB_.PCI0.LPCB.UAR3 > Freefall: > uart0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.LPCB.UAR1 > uart1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.LPCB.UAR2 > uart2 pnpinfo _HID=PNP0501 _UID=3 at handle=\_SB_.PCI0.LPCB.UR12 > > So UID=1 could mean COM1, COM2 or COM3, and that's just on SuperMicro > hardware from the last few years.... > > Adding ACPI (to the UEFI-only boot loader, nothing else) would allow us to > go search the UEFI tree for the PNP0501 node with the right _UID. It's > kinda a heavy lift though. > > I thought about adding something that would set a FreeBSD-specific env var > that would give the loader.efi a hint to make things work on the second > boot (the first boot setting it in rc.d somewhere). But that's a fragile > solution at best, and wouldn't solve the serial installer issues. > > Warner From owner-freebsd-arch@freebsd.org Tue Jun 26 12:39:17 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 217D31024B89 for ; Tue, 26 Jun 2018 12:39:17 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9E1928EB45 for ; Tue, 26 Jun 2018 12:39:16 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: by mailman.ysv.freebsd.org (Postfix) id 545A41024B88; Tue, 26 Jun 2018 12:39:16 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 429961024B87 for ; Tue, 26 Jun 2018 12:39:16 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C344A8EB44 for ; Tue, 26 Jun 2018 12:39:15 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 1165729EE5 for ; Tue, 26 Jun 2018 14:39:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1530016747; bh=PfOv55/KEB/v4oF8ZQMRKeMhs6ZkSlFQOruTJZUNbIY=; h=To:From:Subject:Date; b=J8UMbHqveeJMJCtWsQaKjptCF4bYDtwH++f2KWCVmTT0CFMtnATeHOFY8ryq9Dm6L 5pbxl171gccggeCEbUm5oY17rHa/9WFNSbi5s/LMSNfuSkL4DMuRsXLzYWKy+AL6gi qUkqnRBrKymTD2QTzKMYx3SleGRIlaIHeKvNPzWvprgXvB1ice7JmZ5cD/NCwKETCK IsQtBrq/Ag0y4Jg+K6YB05BOvs6cV0ujvTSx66zZ78TmkBOs/t994OwYE8JkOUOERg A2QAdq513CcN++olqkwuzqgkuKLXXH7s/wmFXiQEWvjE1bd3VpGOxxl+2VyVqNPInn WpGupljy4eY7A== X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJnkw1TuADdE for ; Tue, 26 Jun 2018 14:39:06 +0200 (CEST) To: arch@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1530016746; bh=PfOv55/KEB/v4oF8ZQMRKeMhs6ZkSlFQOruTJZUNbIY=; h=To:From:Subject:Date; b=Yr8t7AA2PVOzJih4cgjGGdYa4OGQ5G5o2u6+dnBquTbufEEEKQDvhAVwxvP6NUABV 5Jv7HxRpMCvlrHj7+tOv0Bo0F5R+dj5JgsNbqLxVnJDqih4s0cU4No0nTVfauvDtAi JltEuRw5XmFRuoBX81uUL4UAczeN5IxfKm/tcsomv6wYuPJpSj7p2sKmtJtvVqKIH1 Imw4RGQxMLWAaNXTpK5lfXbC6/0rkaGCBcxsj2AaZclOg9ntP5R+asdN7gHn31sbLH fRIcfxJ1StxGRfZm3khzcY/DoJw97TXpptTyj2mkeg3ZmYunjOcVfJ1AxDx5Lpaz8f /iDHvzXPtMq4g== From: "Peter G." Subject: What's the status of all the work on loader? Confused by several projects Message-ID: Date: Tue, 26 Jun 2018 14:39:01 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2018 12:39:17 -0000 Good day, what is the current "chief" project focused on improving UEFI support, including ZFS and GELI? Recently Waren Losh unveiled his plans on loader changes. Projects I've been following: https://reviews.freebsd.org/D12692 https://reviews.freebsd.org/D12698 https://reviews.freebsd.org/D12732 https://reviews.freebsd.org/D13497 and more recently: https://reviews.freebsd.org/D15743 and now Waren's recent: https://reviews.freebsd.org/D15917 How do these overlap? Or put differently, when can we expect UEFI support with ZFS boot and GELI full disk encryption? ELI5! Many thanks! Peter From owner-freebsd-arch@freebsd.org Tue Jun 26 12:42:55 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E8981024E27 for ; Tue, 26 Jun 2018 12:42:55 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C74288EEB1 for ; Tue, 26 Jun 2018 12:42:54 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: by mailman.ysv.freebsd.org (Postfix) id 87A091024E26; Tue, 26 Jun 2018 12:42:54 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 763DC1024E25 for ; Tue, 26 Jun 2018 12:42:54 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 068928EEAD for ; Tue, 26 Jun 2018 12:42:54 +0000 (UTC) (envelope-from freebsd@disroot.org) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 2118B29D9E for ; Tue, 26 Jun 2018 14:42:53 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1530016973; bh=UH8QulZOSYYMA60Jkt93nZflYmJWTexcvemhX4uTJsE=; h=Subject:From:To:References:Date:In-Reply-To; b=lpUInsci6o/BLHMQwGp+2I7wdkc6Ubq58BRvUZVfQTvWd/++3JgXdp46k8B7JRMKp vWhQq1NwVNqVYh4Xy+MI6NwYoBeSJfdvvOnA3P8YMDN80ZYXaMiD39ilzNM0ZqNPxI cxVI9p4/h5NHHhVWxu6mcNs6SmaNmWDZzkmTSIgXj8jNpm7P2Bzf4pKGAlw4EIocm+ zTR4P1w98Q9uJidJfEgTiwqLnJuWSmMczcMGD4bQCmYuIyQqLpnARDZ7zkIuDpk20v c3qzjgm2JB5ixBUDAclsZGQND0c5lkWEcRm6Hl84UsLcLr3HZlrhdXNfSXnUvLej4P 4JAq9hYRVTazg== X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rOTMo-ACbk2s for ; Tue, 26 Jun 2018 14:42:52 +0200 (CEST) Subject: Re: What's the status of all the work on loader? Confused by several projects DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1530016972; bh=UH8QulZOSYYMA60Jkt93nZflYmJWTexcvemhX4uTJsE=; h=Subject:From:To:References:Date:In-Reply-To; b=uyYYkWqEEKIkgSpdh/9zZXIDSg9hQn1XM8wlXIaAJdtY8I4jx7G4HUFh24L9n2nta SipYmfBUfuQC+F0pN0Cb1W7lDTj1ytEiRIml14FxTFUMWTkCu5m+4PKivSttl4ho7P o9cfTYEB1f3qVHrNElW+VvqEaYG4bQg2BcPnriOZTb2Oy6X/ggTLsUyR2wIgX0GSNc V1664ncc0c9wReXB9KwYE6NeaCRGUjMegc5oeEHSk/H72hAm2XHGTafIyu+RMlBMx3 o/Y5E2fPbuMkWv84+2tLEnh/JgXkUivl2qlYKqFFqd5uc2IsYpUjsayxCdBX533r9R GTBUTgD6qlavA== From: "Peter G." To: arch@freebsd.org References: Message-ID: Date: Tue, 26 Jun 2018 14:42:48 +0200 Mime-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2018 12:42:55 -0000 On 26/06/2018 14:39, Peter G. wrote: > > what is the current "chief" project focused on improving UEFI support, > including ZFS and GELI? Recently Waren Losh unveiled his plans on loader > changes. Correction: Warner Losh Please excuse the mistake From owner-freebsd-arch@freebsd.org Wed Jun 27 03:32:05 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DA38102AEB6 for ; Wed, 27 Jun 2018 03:32:05 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 16A8790D24 for ; Wed, 27 Jun 2018 03:32:05 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id CE678102AEB5; Wed, 27 Jun 2018 03:32:04 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC32C102AEB1 for ; Wed, 27 Jun 2018 03:32:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6DF90D20 for ; Wed, 27 Jun 2018 03:32:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x231.google.com with SMTP id j5-v6so201070ywe.8 for ; Tue, 26 Jun 2018 20:32:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hRG2mSKhMZbnMJGDFgPokDGYJDpyec5qnYemKz9/eRo=; b=gCPqgQYKmc2dk/2CFZqWEMeHn/o2iHyNMjpw53nqPqzFrujp/AQB4cqboyyXqHADcS 3/y+HRm8gunsPhD9++39+EvHm6f+yD5KsnTVDMpoojk07/BG5Mmudoayt90czbOUbV7M huSCdZSY9s7TFq3Jh8mxLGohUYspQoE7Gvnfs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hRG2mSKhMZbnMJGDFgPokDGYJDpyec5qnYemKz9/eRo=; b=CqEoI9NSRx62De1Vl/85JOG/ZRnFHT0nBONk/puBlHnG4Cp5rcMQVRftO5IKZRp2q3 ohfLHChxr5d/YDjKIu1rCGsY5kgXhvAXrp5rLCDqCHMBLPoYT+u8RCKUkHtZ7s2+b+Wt e+K5oH/0EF+mWYtu9eQkuvHTHEuMJmgjbyEvUAyCuoTpgIpFxptfva2FmGrMAwHPgFUM fR++6wHybxFJUScUczzwdZEnG5Tw5eX9KBZh4+oK2f35aAlohW8O3Ic/D3GNwNvjSJKm 3yrRQq21viKLRMUcwd5c1Ml6knl/Pj3+4pFqjGVhXgVGkx6aEjI2Bp+k+HBwjYihaOxQ E+qQ== X-Gm-Message-State: APt69E1sShQ2BiCPGXPNpQb22YKJrAQs2FtNIzy9oZtqNHyrulry+5gI 3KN6HqAHjwKEjWkzq5WmB6URLq/YMjuxRhGq7mV4qA== X-Google-Smtp-Source: AAOMgpfEHnJ6J+I/dlC65NYgcX7Vft7SBuo6X4jGIxjp2VvooHWTnUBkTvhy9kMOr/KMKPPwlsyuXcsNEO2QA+hWLnE= X-Received: by 2002:a81:af1d:: with SMTP id n29-v6mr2037432ywh.113.1530070323572; Tue, 26 Jun 2018 20:32:03 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Tue, 26 Jun 2018 20:31:32 -0700 (PDT) In-Reply-To: <20180624121412.GY2430@kib.kiev.ua> References: <20180624121412.GY2430@kib.kiev.ua> From: Eitan Adler Date: Tue, 26 Jun 2018 20:31:32 -0700 Message-ID: Subject: Re: What to do about rcmdsh(3) ? To: Konstantin Belousov Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 03:32:05 -0000 On 24 June 2018 at 05:14, Konstantin Belousov wrote: > On Sun, Jun 24, 2018 at 03:32:13AM -0700, Eitan Adler wrote: >> Now that the rcmds are removed from base, it opens a question about >> what to do with rcmdsh(3). >> This is documented as >> rcmdsh ??? return a stream to a remote command without superuser >> And is implemented as a rather simple wrapper of getaddrinfo and exec. >> >> This isn't something I'd imagine we'd add to libc now-a-days and is >> currently broken by default (due to defaulting to _PATH_RSH) >> >> I'm not sure there is much value in keeping this function around. I >> did a rather naive search for uses of this function in ports and >> couldn't find any. I'm preparing a more comprehensive patch for an >> exp-run. > There is a huge value in keeping ABI compatibility. The symbol must be kept. > You may remove default version for the symbol if you are so inclined. I'm new at this. How does one do that? -- Eitan Adler From owner-freebsd-arch@freebsd.org Wed Jun 27 06:53:26 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A327B100A521; Wed, 27 Jun 2018 06:53:26 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 276C197878; Wed, 27 Jun 2018 06:53:26 +0000 (UTC) (envelope-from pratiy0100@gmail.com) Received: by mail-ed1-f46.google.com with SMTP id l23-v6so2411630edq.0; Tue, 26 Jun 2018 23:53:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=/dYAofooBNKaAYt8uPkt8XXQKDobjzOLNBe7CQXixn4=; b=uKFhYp6Ds1PWX+mWBvTGu0F+CVtpMerCJXWC0Sl9JlKVIeXoOjV1EL+AeUddv1f6k6 GMtfhATwZdOrD9gkNkSZI8kyZhC0Jj2z2Lq8ww9q7U3aT7nZjNXT/nhv8CvXgRRYQS2g oAuHJHe3FoFPWqMJ4euFQGKPBG16sK/AsEQjRfLyRkspS5mCms7tqAmoVVBMyEse0Vez 8M1Pljrdck23eibmFLGTOAd+lq5Nv3u6APhYCqWVeZTiSGQo+wRuMOcTW6TtuuruMe9p wQTKAMX1TN3fwJuVb4dWt4sbg4I4cUuVjjv2D0Y0zCestF/a6aWrp7pVX2P3SRCK0k7z /Hhw== X-Gm-Message-State: APt69E1NOEpn+KsgYetGeAf2Np/1t99E1lCvWpesgT0H01rraYzuifZU 5tVB4ktevdZn+T2jYYd3tjBS4PvY X-Google-Smtp-Source: AAOMgpftmax7ut9E+pOn4R/nHidfJhC6Cl60DntstbPpZkdBwLg6IRe7L/1kulFIsganrDClYBwhlQ== X-Received: by 2002:a50:8ad5:: with SMTP id k21-v6mr4476772edk.36.1530082399580; Tue, 26 Jun 2018 23:53:19 -0700 (PDT) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com. [209.85.208.46]) by smtp.gmail.com with ESMTPSA id l37-v6sm1669154edc.49.2018.06.26.23.53.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Jun 2018 23:53:19 -0700 (PDT) Received: by mail-ed1-f46.google.com with SMTP id g12-v6so2403075edi.9; Tue, 26 Jun 2018 23:53:19 -0700 (PDT) X-Received: by 2002:a50:b16f:: with SMTP id l44-v6mr4403117edd.306.1530082399305; Tue, 26 Jun 2018 23:53:19 -0700 (PDT) MIME-Version: 1.0 From: Pratyush Yadav Date: Wed, 27 Jun 2018 12:22:42 +0530 X-Gmail-Original-Message-ID: Message-ID: Subject: Can bus_dmamap_unload() be called before the load completes? To: freebsd-hackers@freebsd.org Cc: freebsd-arch@freebsd.org, =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , Edward Napierala , Akshay Jaggi Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 06:53:26 -0000 Hi everyone, I am currently working on an alternate bus_dma(9) implementation for use with the Xen drivers [0]. I have a question regarding how the bus_dma(9) interface is expected to be used: If the load is deferred because of a shortage of resources, is it "legal" to call unload before the load completes? In my implementation, if unload is called while the load is waiting for resources, it would result in a segmentation fault and leak memory. Do I need to handle that possibility, or is it ok to assume that unload won't be called before the load completes? Regards, Pratyush Yadav [0] https://wiki.freebsd.org/SummerOfCode2018Projects/ImportXenbus_dmaFromOpenBSD From owner-freebsd-arch@freebsd.org Wed Jun 27 07:09:22 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5D05100E0AB for ; Wed, 27 Jun 2018 07:09:22 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 383C7700C6 for ; Wed, 27 Jun 2018 07:09:22 +0000 (UTC) (envelope-from darius@dons.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id EC8BE100E0AA; Wed, 27 Jun 2018 07:09:21 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAF77100E0A9 for ; Wed, 27 Jun 2018 07:09:21 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail03.adl2.internode.on.net (ipmail03.adl2.internode.on.net [150.101.137.141]) by mx1.freebsd.org (Postfix) with ESMTP id ECC91700C5 for ; Wed, 27 Jun 2018 07:09:19 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ppp121-45-48-103.bras2.adl4.internode.on.net (HELO midget.dons.net.au) ([121.45.48.103]) by ipmail03.adl2.internode.on.net with ESMTP; 27 Jun 2018 16:34:01 +0930 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.1/8.14.9) with ESMTPS id w5R73nJP068862 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 27 Jun 2018 16:33:55 +0930 (ACST) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.1/8.14.9/Submit) id w5R6jBfH056980 for ; Wed, 27 Jun 2018 16:15:11 +0930 (ACST) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f Received: from [203.31.81.59] ([203.31.81.59]) by ppp121-45-48-103.bras2.adl4.internode.on.net (envelope-sender ) (MIMEDefang) with ESMTP id w5R6j5Uv055936; Wed, 27 Jun 2018 16:15:11 +0930 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: What to do about rcmdsh(3) ? From: "O'Connor, Daniel" In-Reply-To: Date: Wed, 27 Jun 2018 16:15:04 +0930 Cc: Konstantin Belousov , "freebsd-arch@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <27EE2F1E-245C-4D97-97DE-65E9DA133AF1@dons.net.au> References: <20180624121412.GY2430@kib.kiev.ua> To: Eitan Adler X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Score: 1.5 (*) No, score=1.5 required=5.0 tests=HELO_MISC_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.0 X-Scanned-By: MIMEDefang 2.75 on 10.0.2.1 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 07:09:22 -0000 > On 27 Jun 2018, at 13:01, Eitan Adler wrote: >=20 > On 24 June 2018 at 05:14, Konstantin Belousov = wrote: >> On Sun, Jun 24, 2018 at 03:32:13AM -0700, Eitan Adler wrote: >>> Now that the rcmds are removed from base, it opens a question about >>> what to do with rcmdsh(3). >>> This is documented as >>> rcmdsh ??? return a stream to a remote command without superuser >>> And is implemented as a rather simple wrapper of getaddrinfo and = exec. >>>=20 >>> This isn't something I'd imagine we'd add to libc now-a-days and is >>> currently broken by default (due to defaulting to _PATH_RSH) >>>=20 >>> I'm not sure there is much value in keeping this function around. I >>> did a rather naive search for uses of this function in ports and >>> couldn't find any. I'm preparing a more comprehensive patch for an >>> exp-run. >> There is a huge value in keeping ABI compatibility. The symbol must = be kept. >> You may remove default version for the symbol if you are so inclined. >=20 > I'm new at this. How does one do that? You could just leave the call, I assume it will fail with an error if = rsh isn't in the path. If a user desperately needs it then they can install an rsh from ports = (or something). -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From owner-freebsd-arch@freebsd.org Wed Jun 27 17:08:15 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CEAB102D9D6 for ; Wed, 27 Jun 2018 17:08:15 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCB78875E2 for ; Wed, 27 Jun 2018 17:08:14 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 87CB51DF98 for ; Wed, 27 Jun 2018 17:08:14 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id C012D96BC for ; Wed, 27 Jun 2018 17:08:13 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id b4AzNocPuBWb for ; Wed, 27 Jun 2018 17:08:10 +0000 (UTC) Subject: Re: Building and Iterating DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com A007796B7 To: freebsd-arch@freebsd.org References: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8CGwwF AlrozigFCQpgez0ACgkQNddxu25Gl8+m5Af/R3VEdxNMAcDIes9ADhQyofj20SPV3eCJ3HYR OebTSuNdOudGt4AAyA8Ks94u9hiIp5IGsc6RDsT9W7O2vgXhd6eV3eiY5Oif5xLIYrIDVu1Y 1GyRxRrPEn/QOqDN6uFZCPwK1aOapGcYCrO9lB0gMuTVfgHanU61rgC9tMX0OoAOyRd+V3/M 8lDNhjJdF/IpO3SdYzKfkwduy4qamw4Gphcx/RfYQvYLq/eDkP8d50PphWdboqWBwNRHayro W/07OGzfxM5fJ5mBsXPQcO2QcRjkyHf6xCM6Hi1qQL4OnXMNE/ZTX0lnOj1/pH93TlzSHZMP TaiiA/MBD3vGsXBmBg== Organization: FreeBSD Message-ID: Date: Wed, 27 Jun 2018 10:08:11 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 17:08:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb Content-Type: multipart/mixed; boundary="19a1ModR1MTu60mUXgFqei6jDjqMHl39b"; protected-headers="v1" From: Bryan Drewery To: freebsd-arch@freebsd.org Message-ID: Subject: Re: Building and Iterating References: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> In-Reply-To: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> --19a1ModR1MTu60mUXgFqei6jDjqMHl39b Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/20/2018 2:00 PM, Bryan Drewery wrote: > On 6/1/2018 10:20 AM, Sean Bruno wrote: >> Before I dive into the mk files of a buildworld, I'd like to describe >> "what I want" so as to start a discussion of my goal. >> >> 1. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to b= e >> built, only build a toolchain that targets the ARCH being requested. >> >> 2. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to b= e >> built, give me a knob to turn that aborts the build with a meaningful >> message that lets me know I need to update the toolchain on my buildbo= x. >> >=20 > https://reviews.freebsd.org/D11077 has this but I suspect it's wildly > stale already. >=20 > Also having a knob like this would ultimately lead to someone making > their /usr/bin/cc less useful for optimizations like WITH_SYSTEM_COMPIL= ER. >=20 >> 3. If the boostrap toolchain needs to be built in the normal case, on= ly >> target the ARCH being requested. I understand that we "want" a CC >> installed that targets all architectures and this is something I agree= with. >> >=20 > Hm yes there is no real reason to have multi-arch support in the > WORLDTMP compiler. Though I do have a pending patch to build clang > *once* for universe that relies on this full-arch-support behavior but > I'm sure it's trivial to continue using it for that piece. >=20 >=20 For the archives, a lot of this is effectively done now. See https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069994.html= --=20 Regards, Bryan Drewery --19a1ModR1MTu60mUXgFqei6jDjqMHl39b-- --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJbM8R8AAoJEDXXcbtuRpfPZLkH/0ogywC+bMM0sIjtT3auzv7e 8ugFAXo04UCu/bcE81714BsTbTTHmE5wYAPjYWIHge8v6gwC2HIW6qkJEJ7lepvg HJtleatabIitvbgI1Palg7Z/XCZYQUea6YgkmuaxZF6PSyH7qRtJS++oTgWgOopR HuywnDHO/yWSDMmy/6PWSGod3Xb4LFZq/39w2gKJCxYMyZv1vMHpX17h6yYI1ziV WW4xBzfOUY/yhsNgr2vvzwEPIzok/V4UYu80zh0sOX5FIEo3xx1vRh0cuWjgKt0N 6b9tMbBCUdNj9Em2A8YoEFNki88KTmI5edC84PCKAmT05reWPjO/cy0d/OX9HqU= =TAlw -----END PGP SIGNATURE----- --CY5ujk00OEU3IABn47xLFZAJhMYfv4jMb-- From owner-freebsd-arch@freebsd.org Wed Jun 27 21:15:42 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D386A1012178 for ; Wed, 27 Jun 2018 21:15:41 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4E28673D8E; Wed, 27 Jun 2018 21:15:41 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-234-146.albq.qwest.net [67.0.234.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id A8CE61AF636; Wed, 27 Jun 2018 13:19:37 +0000 (UTC) Subject: Re: Building and Iterating To: Bryan Drewery , freebsd-arch@freebsd.org References: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: Date: Wed, 27 Jun 2018 15:15:31 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PK2QOX0QXKXKNyu2r85rOcG9gMZGGgNEL" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2018 21:15:42 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --PK2QOX0QXKXKNyu2r85rOcG9gMZGGgNEL Content-Type: multipart/mixed; boundary="Rw068grnuDJiUmJQ84nVh8CHtFaxrpyDu"; protected-headers="v1" From: Sean Bruno To: Bryan Drewery , freebsd-arch@freebsd.org Message-ID: Subject: Re: Building and Iterating References: <686cb08d-5648-52f4-a95e-2faf3ea20bef@FreeBSD.org> In-Reply-To: --Rw068grnuDJiUmJQ84nVh8CHtFaxrpyDu Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06/27/18 11:08, Bryan Drewery wrote: > On 6/20/2018 2:00 PM, Bryan Drewery wrote: >> On 6/1/2018 10:20 AM, Sean Bruno wrote: >>> Before I dive into the mk files of a buildworld, I'd like to describe= >>> "what I want" so as to start a discussion of my goal. >>> >>> 1. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to = be >>> built, only build a toolchain that targets the ARCH being requested. >>> >>> 2. If I select no toolchain (WITHOUT_TOOLCHAIN), but clang needs to = be >>> built, give me a knob to turn that aborts the build with a meaningful= >>> message that lets me know I need to update the toolchain on my buildb= ox. >>> >> >> https://reviews.freebsd.org/D11077 has this but I suspect it's wildly >> stale already. >> >> Also having a knob like this would ultimately lead to someone making >> their /usr/bin/cc less useful for optimizations like WITH_SYSTEM_COMPI= LER. >> >>> 3. If the boostrap toolchain needs to be built in the normal case, o= nly >>> target the ARCH being requested. I understand that we "want" a CC >>> installed that targets all architectures and this is something I agre= e with. >>> >> >> Hm yes there is no real reason to have multi-arch support in the >> WORLDTMP compiler. Though I do have a pending patch to build clang >> *once* for universe that relies on this full-arch-support behavior but= >> I'm sure it's trivial to continue using it for that piece. >> >> >=20 > For the archives, a lot of this is effectively done now. See > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069994.ht= ml >=20 >=20 Good lord Bryan. Thank you. sean --Rw068grnuDJiUmJQ84nVh8CHtFaxrpyDu-- --PK2QOX0QXKXKNyu2r85rOcG9gMZGGgNEL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlsz/nNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /LY9ZAgAoSdKLlXYZrWsfIvBRUHz0eegdga8lMhvr+Bel02I8UEl8I7YRO9aKcp3 +j/RnwTkDIj7y5kMsMpNfwbYYFJudF8TgGeAJ5shy1ANtBk1enkU7xrqO9dmWqwR Au0gzY59zSsp3R1K65+7tUHF5xNbkrFqPUqEcjjDHin/qQWfLRaKcVWZPyPzbBNA ea2TlDIzeUwQJHLXaCw70AnKypHPQep6qjcEcwy8ckpOq2WEsptVAOmjQF4KULZj lr/7X/PaDkI5sNWyeSYMssLQpuGdWdsW9Vk8pm78zeETv0TN7BiTqBa3Wy/t1dIY G9J7rfp4HG0k5l+td6t937IkU63zwQ== =s/du -----END PGP SIGNATURE----- --PK2QOX0QXKXKNyu2r85rOcG9gMZGGgNEL-- From owner-freebsd-arch@freebsd.org Fri Jun 29 08:00:26 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28AFF1034349 for ; Fri, 29 Jun 2018 08:00:26 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B158580EA5 for ; Fri, 29 Jun 2018 08:00:25 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 67E5B1034348; Fri, 29 Jun 2018 08:00:25 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 454CC1034341 for ; Fri, 29 Jun 2018 08:00:25 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7E5E80EA1 for ; Fri, 29 Jun 2018 08:00:24 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22a.google.com with SMTP id w13-v6so3102874ywa.5 for ; Fri, 29 Jun 2018 01:00:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=Kn28wyWKx9423cTVrRmoVCVjuh9pfOEBORHzi+nngxo=; b=Jm3ztOz7OExPkKtR4F1YI4O0FFA/l58pJLDQIYkDZNK9JChUBVaYfAmoOrH3ejGqLI fFcWLBlhcfcwjWZVe1d9vLh0BDAMKnziYomrHtT88pFof9lHvVNQvg6MQaz1MCRl/5pn h8LDr2CzqZySv5I1yF0rls+YYTxZExb01nlGc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=Kn28wyWKx9423cTVrRmoVCVjuh9pfOEBORHzi+nngxo=; b=oVtmjCyOJfkIrhBVeeodA23vsV5L/gwOfqPCCjxffmOtjCkgjrB4zn4F/MC3Dolrul dFDCRfCvgXVvGHnHY+7VmisOcXoCJ+kpBmBgqCftYuQQl9hzNe0yHv7M3aa28WhGEm7/ wb5FZeykiHsoI7S1faiF8geKMNBOom6jjblDoXSNU/QZLqsZ8mSJXuv+jxbE91f5swMi HzejGvAXV2NjcHeTlTDYc9XFtqkjPShuI8ZhEPC1UOuC7H7M+SFWwVen9AmPepr4iv+n ClP36mitho8hbamorIp5xZKnI84rGoIpq9mkgDmtISPCbndQzoxpgEdaqKW4zDJMUoaE HneQ== X-Gm-Message-State: APt69E1HMd21iKBsXJyD7ny0zf0Bjh0vrnH/tsj2yPSETRltpUXBolCQ 2wmYO6lgTIOQLmuxghaHCdkfWFU1w7eYq7lMIQvLENtU X-Google-Smtp-Source: AAOMgpeQpm3No+qVhodQ48tyrDBnbQn49MOEXEOwYQiYHZXOvkWERCM2ud2DkQURC+9i0xZ5hRyZ6t7Jm8JzSt4t0Zo= X-Received: by 2002:a0d:e848:: with SMTP id r69-v6mr6829826ywe.19.1530259223894; Fri, 29 Jun 2018 01:00:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Fri, 29 Jun 2018 00:59:53 -0700 (PDT) From: Eitan Adler Date: Fri, 29 Jun 2018 00:59:53 -0700 Message-ID: Subject: C++ in the kernel? To: "freebsd-arch@freebsd.org" , David Chisnall , Justin Hibbits , Maxim Sobolev Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 08:00:26 -0000 This was the contents of a conversation on a different list. Figured it was more appropriate here: >> We are experimenting with a C++ library for systems programming and are = interested in trying it in the FreeBSD kernel. Has anyone managed to run C= ++ code in the kernel before and perhaps have patches to make the kernel he= aders somewhat less C++-hostile that they=E2=80=99d be willing to share? >> A friend gave a WIP talk at BSDCan a few years ago doing this very thing= . You can find his work at https://github.com/adamlsd/libcpp.ko >> I believe few times I've seen this discussion over the years the main co= ncerns raised were uncertainty about handling of exceptions and also lack o= f the real stable ABI for the C++. Each compiler seems to have its own conv= entions, which might vary even between compiler revisions. https://youtu.be= /JPQWQfDhICA?t=3D51m55s What might be possible, however, is to have particu= lar C++ "runtime" as a module itself, which is then would be used by the ot= her modules that are compiled with that particular C++ compiler. >> Most kernels that use C++ require -fno-rtti -fno-exceptions, so don=E2= =80=99t rely on a runtime. The ABI concerns were a problem 20 years ago, b= ut *NIX systems have kept the same C++ ABI since everyone[1] adopted the It= anium ABI. [1] Well, almost everyone. AArch32 has a slightly different AB= I, but it has also been stable for a similar length of time. >> Thanks, the include directory of that repo looks to be exactly what I ne= ed to get the subset of libc++ that I need working. --=20 Eitan Adler From owner-freebsd-arch@freebsd.org Fri Jun 29 14:14:42 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 916FCEF8DEA for ; Fri, 29 Jun 2018 14:14:42 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 22CC98CD3F for ; Fri, 29 Jun 2018 14:14:42 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id D757BEF8DE6; Fri, 29 Jun 2018 14:14:41 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4CE8EF8DE5 for ; Fri, 29 Jun 2018 14:14:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F4AD8CD37 for ; Fri, 29 Jun 2018 14:14:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x236.google.com with SMTP id r3-v6so3412232ybo.4 for ; Fri, 29 Jun 2018 07:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=ZjzBi1zAUIYAqye8y5dNJDMzgQLOM3yeU44v2KToj1Q=; b=TBzdqPSMx7pczVeluR3ZUo9OU5tQ4coe7loARABHwZfu0UInd8uwm43/OkzUqMeDiC Q2yFPab3wLnsncNcwXm8mRsQF7z/MWkun6adcquHpNWVPPiPp/LjOPBhxrMiw34DjgaH +XKmeEfx3+oSLbtuvkFo95c5d3d94guvWe2Ws= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=ZjzBi1zAUIYAqye8y5dNJDMzgQLOM3yeU44v2KToj1Q=; b=kt/HEYK1yNEwt9gUZr1uM/fJvhXc//03lt6GSKs8DS2DeCrCupvvxhkreCm4lDgGBL ABVEp4e2a74FmYkIBLQGEEDFRd7cGodbzHQ6moy1l02r0QY+/Jxek5kJjEgm1sZAGB/F s9eXYz+rBYGfrGgGKhqov5+q7qxBXdx2Eg+95//hVnR2IHaIpYyyCQhvjgrjL8qN/FSR tNdqQsrWBA7CA34vO+Nhx94NO/LEJkrltllCssRDcfcOvnLFGUcVvfnjGDShWpFxS6en TtXMmKQA8/WEmR6MmQlBi7Ocg5ph2eLFKqRpOhVyViYS0zjLp0pERjai1oDcs9yRLfhr A6Fg== X-Gm-Message-State: APt69E14dn3wXzvEBI8tP1wCSOVh3Quy2iLMPfeAAY9MkY1V6AaaI+lw YD03unQWSaR/C0fNFFy0UbtEDnoY4IEvp/5CLCa0tg== X-Google-Smtp-Source: ADUXVKKma1X4we7KNCVJUgRk/KUNULMun/evWNcRxq77qZl+zH6/p1MNOVGJvTHBrpd7SLhqLbROx2Djk3TNDcg6jtw= X-Received: by 2002:a25:9b09:: with SMTP id y9-v6mr7540449ybn.194.1530281680474; Fri, 29 Jun 2018 07:14:40 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Fri, 29 Jun 2018 07:14:09 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Fri, 29 Jun 2018 07:14:09 -0700 Message-ID: Subject: Re: C++ in the kernel? To: "freebsd-arch@freebsd.org" , David Chisnall , Justin Hibbits , Maxim Sobolev , "Kenneth D. Merry" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 14:14:42 -0000 On 29 June 2018 at 00:59, Eitan Adler wrote: > This was the contents of a conversation on a different list. Figured > it was more appropriate here: > >>> We are experimenting with a C++ library for systems programming and are= interested in trying it in the FreeBSD kernel. Has anyone managed to run = C++ code in the kernel before and perhaps have patches to make the kernel h= eaders somewhat less C++-hostile that they=E2=80=99d be willing to share? > >>> A friend gave a WIP talk at BSDCan a few years ago doing this very thin= g. You can find his work at https://github.com/adamlsd/libcpp.ko > >>> I believe few times I've seen this discussion over the years the main c= oncerns raised were uncertainty about handling of exceptions and also lack = of the real stable ABI for the C++. Each compiler seems to have its own con= ventions, which might vary even between compiler revisions. https://youtu.b= e/JPQWQfDhICA?t=3D51m55s What might be possible, however, is to have partic= ular C++ "runtime" as a module itself, which is then would be used by the o= ther modules that are compiled with that particular C++ compiler. > >>> Most kernels that use C++ require -fno-rtti -fno-exceptions, so don=E2= =80=99t rely on a runtime. The ABI concerns were a problem 20 years ago, b= ut *NIX systems have kept the same C++ ABI since everyone[1] adopted the It= anium ABI. [1] Well, almost everyone. AArch32 has a slightly different AB= I, but it has also been stable for a similar length of time. > >>> Thanks, the include directory of that repo looks to be exactly what I n= eed to get the subset of libc++ that I need working. Copan used C++ in the kernel to support RAIDCore, which was a software RAID stack. (Written by ex-Adaptec people, I believe they were acquired by Ciprico, which was then acquired by Dot Hill, which was acquired by Seagate. No idea whether the software is still active/maintained.) RAIDCore didn't use new/delete or exceptions, so it wasn't too difficult to get it running in the kernel on FreeBSD. (It was originally written for Windows and then ported to Linux, and we later ported it to FreeBSD at Copan.) The porting effort probably happened in the 2007-2008 timeframe. RAIDCore was proprietary and the support code was never open sourced, so there's nothing to share unfortunately. I don't think there was much to it, but my memory on that is fuzzy. I guess the point is basic C++ in the kernel can be done without a huge effort, and it was in a shipping product for years. --=20 Eitan Adler From owner-freebsd-arch@freebsd.org Fri Jun 29 16:08:02 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FB91EFCC3D for ; Fri, 29 Jun 2018 16:08:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 01FC470A87 for ; Fri, 29 Jun 2018 16:08:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id B0969EFCC20; Fri, 29 Jun 2018 16:08:01 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DA7DEFCC1C for ; Fri, 29 Jun 2018 16:08:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BAE170A78 for ; Fri, 29 Jun 2018 16:08:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id k17-v6so2679058ita.0 for ; Fri, 29 Jun 2018 09:08:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=ITO16nwwKDvHqgvdT0TposN9lg+2jlvOmJPjhLGINUw=; b=NnCz1zNujcJcx2LYT4m9K9SZZ7JxgBSoc7ZTUi51nKtyHvT9MLR0D84SzWsMaUJa1s 6kPYrKnEj4JWHZlCBKmIs/k36LfT3ntWoRuhNPSyY9aVNLRZrbzSEA0tQ3/FHfenoMqY HudkqFy5ffF5n4AzxTiXGKJLGPTBaiKl+ON9p5l3RUZhHRFPO33SvwRgD48jvGqpyQhR tDseSyiGwYcjn6nQ8x3K05s9QNd36qcdbOSzeIZRVa/F00MMXQpIl/D+TOKqHTjqf86y pWtMw3Gj6KU2WCQBHMicMpsBMHR9c4gpVtgTXhz+XMl56dP7CXZUiLiBvMqYTKoX9Nkx n1vg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=ITO16nwwKDvHqgvdT0TposN9lg+2jlvOmJPjhLGINUw=; b=lR+ZOyGNVULVHJMgqHwwDblYKOv6Sd6ANNb2ySTTzQlPbtngk62dKe+MViu6DSmpb9 0pWU6KRtVpSwqYKJ53JaIkhN4pTegkfY/6snxWyFGaTEqNk9kPNl9wYBqk5K8rXISWct TSiJLFDjEOGAH3dkUW7myTQBg8RhWogpPoxVRq5ptBkVT3FNkmcAguyGeW+pm0zjhHa3 kBOZnXUK32qiOaHnJ+3KiDMPL5gMGyFOsXmQj0rTpNBMZhLGHYjNIwCahe4g3b5fgUnI 0FZ4gLWxg+Bx0SsknhkQM/69c7w+oZez9MZfUaGrb75Pkz8paxTgsfTFwVWcMtg02azZ Gcqw== X-Gm-Message-State: APt69E3bdkK6unlKZXYBpvQdIQcrTF12UXz/hZLCLO6Pg2ZZc2JlVYEE v3cqbvLD3ZK1e9UVdPUaDdTb61q+b2tezrkXXQ65mJ/f X-Google-Smtp-Source: AAOMgpcP40jWQHX4mufIcNk1FHH1RynAGpOCTMVScq7+mahZxrXfpH08lJIKt5yU/PPuPvU56X8qGBSEl2+jhjFzOBk= X-Received: by 2002:a02:6001:: with SMTP id i1-v6mr13002403jac.5.1530288479975; Fri, 29 Jun 2018 09:07:59 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Fri, 29 Jun 2018 09:07:58 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] From: Warner Losh Date: Fri, 29 Jun 2018 10:07:58 -0600 X-Google-Sender-Auth: gWZEIumTJZTrhJC_ZyFHnDL-iAI Message-ID: Subject: dd conv=direct patches To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jun 2018 16:08:02 -0000 Greetings, I've added the ability to specify O_DRECT to dd in these patches:: https://reviews.freebsd.org/D16064 Please let me know what you think. Warner