From owner-freebsd-hackers@freebsd.org Sun Dec 13 17:27:35 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 02A794BEE24 for ; Sun, 13 Dec 2020 17:27:35 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvBKy0hmpz4flF for ; Sun, 13 Dec 2020 17:27:33 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-x330.google.com with SMTP id w3so13434117otp.13 for ; Sun, 13 Dec 2020 09:27:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Qf/Et/P3ZPPLt4azw3SbzVT47MuXZiYKiZ9bgRvXS6o=; b=gd+v4tDqNF1bYbLKSRU6aDH176X/q/m266fLmg5LBDnGm1i/5z8PPavL4CYVPeOX77 yZAupHL6yDZgrfIMekuoQX5Jm8KsFyXJr3X2WZy9Ce06lIIdoU+JjJQfRC3KSMlwI1ie WIOFs11sNYnhAA45LnmcAXt6GHRz01GGHsrf9IQHIXN1pzt+XKeQ1GumZo02rONjSNKO Qn/Vu1e3vr5F7+uFqiyUqWe3UcKDS2FMpY5vpa4ktd+34BB6m3T+t2PMGPRHJ5AH48uA Slqh7wj2oJzDRBcrC61B5Peji6hx4fa2bCXjBYkTtX+/i2kjNs+lDQuOPXQ+cjjuXQNl ulgw== 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=Qf/Et/P3ZPPLt4azw3SbzVT47MuXZiYKiZ9bgRvXS6o=; b=iGJxJ4XVKEcjlzaV9bhP5V2Q3JRONUXEBnon9xv3p216r89AxuPUmMr01RBH7/5fvE vu9dbUHrKXVcKu5a1pAcvj96xuB75gRgYEAui1Ue+ekXeP6GDbFgOpsaTxvOa8dBQISR m/gsgvgngW0qZdWsnCuoJ2YiuGonhOlgJ51RFYKeDd5eVlijW5SCGlZI2RZ5R1lyRJ0f k2MTtZJtxucNi05k/VuVw9mlsxhFSq3fcwvsL/Lk+WETF/GS0ppsiANGgR28gavRgvZD x/l23wUXrIilcQnjf+Q0iudm8JKic6WP5NAogUdtgl1j/JrUafBVV6f7F3USXbDTAyaG P+1Q== X-Gm-Message-State: AOAM530YxS+TVwBQHrXYSNf8MDjM/tNRe7c1SV6+e2cU86JE6zElBaqK 0rBpDeo9Rb89GYAHz0xZUYTBBEw6niVZg8XKsOg8A9BE7qw= X-Google-Smtp-Source: ABdhPJztbcBukaB6qFEtsmB1cb74qYwRtuALhzifIXl4HR99s2n+T1tSbe0jadSJgYN0gdbeEy4Uhrk9Y/u+JfxEO6E= X-Received: by 2002:a05:6830:2413:: with SMTP id j19mr8136743ots.251.1607880452673; Sun, 13 Dec 2020 09:27:32 -0800 (PST) MIME-Version: 1.0 From: alan somers Date: Sun, 13 Dec 2020 10:27:21 -0700 Message-ID: Subject: char devices without SI_UNMAPPED? To: FreeBSD Hackers X-Rspamd-Queue-Id: 4CvBKy0hmpz4flF X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=gd+v4tDq; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 2607:f8b0:4864:20::330 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-2.41 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.41)[-0.415]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::330:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FREEFALL_USER(0.00)[asomers]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::330:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::330:from]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 17:27:35 -0000 I'm trying to exercise the aio code that handles character devices that don't set the SI_UNMAPPED flag. But I can't find any. Are there any remaining character devices that don't allow unmapped I/O? -Alan From owner-freebsd-hackers@freebsd.org Sun Dec 13 18:17:52 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EFA2B4BF8E3 for ; Sun, 13 Dec 2020 18:17:52 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound5a.ore.mailhop.org (outbound5a.ore.mailhop.org [44.233.67.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvCS03rDvz4hvj for ; Sun, 13 Dec 2020 18:17:52 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1607883471; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=he/3qM8AIR6dUzV90qETVZp+s+9DneNZuIihNSAfx7X3wAqrexZV2IrvNgt4ah+5ndOlGxtM9//+R fWFFj5U0OvqjZ50p5vE2eldyv65rGo7Xk5yfhLTEYHSFED7REkDQ2wLUsTVPIFG+dDyo2Fo5pbRZow Xyq1BIzVCqRFbqM7cv7lqTJkVTnXkGvt4Gs17xKJyQ/tbuCIBXPov965WoPbd2hFv46z2z6uedFlr8 9p1jiQRUilvhVGP41/Afa/xC9WlU+UnDATaQvSHdp6/sLCIGMcOhatAHrlosH5Hz20CiHdx8orXWxJ WhSGeET01u26PcMsqbgnDAaMZpAaxZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:dkim-signature:from; bh=6hawAtwhkQW2sNr8vSUNUyTpvWvxKdaPvuF8Q5VNfgw=; b=qdbvZ3JbbtUfrINCq5iG4liYlSHfmF8sYirXveS6BJBfPI1UXLL6wWb3gaVOSnZ+XBvZgyRhiRLzx +xJiuZyOc+kuLQVkQJYGLKO2aq23LvMu58V3KvUeMjk08LSw0w+261YaywRQ56QFZIsAm4S5gIiKPY /1eMIVWgYqijMEdfLqTXG9fPke9A0q/5mjdstmK/+tDss9fN5v8jEENfVBEbLmfXjsP0MrsW7bArkc GQPA5+kfZeIsnWDSCXKq2HycMAcdg1HwTDTL9owlN6KDupbfR2caWJNAO8VGkgBhXiSSjmUlWSsyXM ye173oibJLZlKdDFwPcI52fHbP17ToA== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:to:from:subject:message-id:from; bh=6hawAtwhkQW2sNr8vSUNUyTpvWvxKdaPvuF8Q5VNfgw=; b=q5zaX/VuQVsAwSK3XdE0KeCSxQLx70+Lo8naAz27EoPSqJgCSAuRY+fMumnArY4KnySR9Lov5dM+1 8z951lE0PgCqHeP3QcjpzSZ0k/BmigCzh+NYWvEPiGcVpaDJS5iDiawdXcOdid6zzyeXOHt/DxmLSp J95PyAeVpWRVT0yCjdoGNeGXqRgNP6VwL8BT0Gh+LhlOfrT1y4s8D1xhkmlwcGn/ARodacLjujBm1l C0J7pLpa97CO9PYrOQ/uwgomiUzxHFJjV4sOnj78WwCHy2IND6tQQBFCWhXDFZXoFY7oIaUKzkkBwj Dy60dNwfFFSI+c7nZPfzjRYLEcX3VAw== X-MHO-RoutePath: aGlwcGll X-MHO-User: 81934082-3d6f-11eb-8b5f-614106969e8d X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (c-67-177-211-60.hsd1.co.comcast.net [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 81934082-3d6f-11eb-8b5f-614106969e8d; Sun, 13 Dec 2020 18:17:49 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id 0BDIHm1R043156; Sun, 13 Dec 2020 11:17:48 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> Subject: Re: char devices without SI_UNMAPPED? From: Ian Lepore To: alan somers , FreeBSD Hackers Date: Sun, 13 Dec 2020 11:17:48 -0700 In-Reply-To: References: Content-Type: text/plain; charset="ASCII" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CvCS03rDvz4hvj X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:16509, ipnet:44.224.0.0/11, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 18:17:53 -0000 On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: > I'm trying to exercise the aio code that handles character devices > that > don't set the SI_UNMAPPED flag. But I can't find any. Are there any > remaining character devices that don't allow unmapped I/O? > > -Alan > I assume you mean disk-like devices? Probably mmcsd, flash/at45d, flash/mx25l. -- Ian From owner-freebsd-hackers@freebsd.org Sun Dec 13 18:20:35 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A0BE24BFCEB for ; Sun, 13 Dec 2020 18:20:35 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvCW66f0cz4j1v for ; Sun, 13 Dec 2020 18:20:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x72d.google.com with SMTP id z11so13658189qkj.7 for ; Sun, 13 Dec 2020 10:20:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=16fbN5++Egtl3oLjoHIPVpvpKk0kXoEByqnDhnw4B9U=; b=cWRW9aUYvzbSqiUI12CQp3ULeNMlaC5MkX2xJCfHKulyv430XZ4Q690x1/s8oHo2Qp 8qWajJP3CQz3+VrjNSUBPSIr1ajnjngri74+4qkDj6G3ABeED6Fu1hcbaQDNflF5Jp+R dguAYdPgc6kQ8WiFjaPMOiVbFbdU7ZqM4tow7D9yxDwmIGn7cNHk6KGZMI+y2wKLCRQC mO32WF8wl3DZPe1oeDwiPcZcUnsAPClkwh0gdYBxp7WmQm7bzUPzyVaqxj218KUiTNz1 NxDpITdCORkvl9kNf04oOTI5eKdTik7ZVDiHyxoTKbtEvdTIwdUB7L/7BeNxZjyy3zAc QAWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=16fbN5++Egtl3oLjoHIPVpvpKk0kXoEByqnDhnw4B9U=; b=mEkYsVBfOwuG69na0Yx8UPbliGnytAVraE0eXRuROWzdNxPgM6Xa51GdqjCyw36xOe 08ezUDCFjLqY2RCTBgL5E2kh+w1IhcQO3a9YHNtvbapdrNFvMWqbrx2N0hcupGHNjps/ rVuwO7bBeDoUaKV1SFdjCyc8JALp+IIZcb6/jTiWaWvf34K7hivLJBmf/i4LxNg6xojq ZT5PgX5wMDewKdk1nusfihlx3CbqhRKs45feQNqgkFXbX+VzasyMFsdVdyNRjoO3mtyD 8B6tff6a1qj9iaeM3vODu6BzNek6eSrPGdnMHdmV2bwxoL/hOgSDtKHnwgYLgrKTI+4f /g+Q== X-Gm-Message-State: AOAM532up4YatNmsvRztnyPyYuA2qnPFST403VuHrgbYsq6HSgOEDCKT 5wWv3pq79lsBAw2Yge7gf+gsye08wQ6JudPqv0sUow== X-Google-Smtp-Source: ABdhPJzqnZ3TkvaKMCTJRMlAOMaaiXC/BO1Tq8vSywDmuZ5z7ES/0mMhGUAeznldOIyKoNY/hZ0UR1cj8Esgh9NiE6A= X-Received: by 2002:a37:a614:: with SMTP id p20mr28352494qke.359.1607883633583; Sun, 13 Dec 2020 10:20:33 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> From: Warner Losh Date: Sun, 13 Dec 2020 11:20:22 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Ian Lepore Cc: alan somers , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvCW66f0cz4j1v X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=cWRW9aUY; dmarc=none; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::72d) smtp.mailfrom=wlosh@bsdimp.com X-Spamd-Result: default: False [-0.72 / 15.00]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::72d:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_SPAM_MEDIUM(0.28)[0.283]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::72d:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::72d:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-hackers]; FREEMAIL_CC(0.00)[gmail.com,freebsd.org] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 18:20:35 -0000 On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: > > I'm trying to exercise the aio code that handles character devices > > that > > don't set the SI_UNMAPPED flag. But I can't find any. Are there any > > remaining character devices that don't allow unmapped I/O? > > > > -Alan > > > > I assume you mean disk-like devices? Probably mmcsd, flash/at45d, > flash/mx25l. > There are times that it's disabled administratively as well, but that may be on a per-I/O basis. vfs.zfs.vol.unmap_enabled: 1 vfs.unmapped_buf_allowed: 1 "Why do you ask?" is the next question... Warner From owner-freebsd-hackers@freebsd.org Sun Dec 13 19:21:02 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 29D3B4C1518 for ; Sun, 13 Dec 2020 19:21:02 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvDrt06g1z4n19; Sun, 13 Dec 2020 19:21:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id q25so16743657oij.10; Sun, 13 Dec 2020 11:21:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wEBRKarIyIxXJe3U9Srfi+yO4ylyn+7S/LGn9RFpFjw=; b=TK6Paj+Cm260TsETMK/dW+jbPQ+HOPGNY8laGvdVpKf8iOxM4kTBcVq2FI/wjZsbv1 PUj92sD2lz5XQExUha0C1gyQ+xjXyMnstTWVEIwaX1Mzd2XB/77HXEQYHF7+mQJTBYj+ AnFtIfQNgm7+xTbytWtkHwhX0Efc3RT9OuWdYY4B/IbDU/natI+hEaO1YsEch1vagsie 3TnF4ctLkfTrTBN8qZi9br1mYkoOipbgtnGnsQVXkuDNtbXZkeKwErsJnJLcXnVrTEKs ZDwtM5QKczv17uwuh0ubck/jeDpSZhvsVBD4DoSgJnwfAgRNl1ePAaR4JprIvV1/SeQk 2h2w== X-Gm-Message-State: AOAM531Bn2H6dihZzMY1sAEiuz1GpvDxLqIUpCvkIgOGaEaeUVB8Ibkt VAWYDQaABgn4fOYBSsrkEd7+JHOHNJ9kC2LWwon6IcXEdW0= X-Google-Smtp-Source: ABdhPJyChzJHZN/g9YwAFw+Ne15bBnnUaEEePSsjTqeux/e2syu0loUGb4qu3gv9M4WjrEi6FKVY1zQVmYut/viL8j4= X-Received: by 2002:aca:dd09:: with SMTP id u9mr15523427oig.73.1607887260859; Sun, 13 Dec 2020 11:21:00 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Alan Somers Date: Sun, 13 Dec 2020 12:20:49 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Warner Losh Cc: Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvDrt06g1z4n19 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 19:21:02 -0000 On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: > > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: >> > I'm trying to exercise the aio code that handles character devices >> > that >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there any >> > remaining character devices that don't allow unmapped I/O? >> > >> > -Alan >> > >> >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, >> flash/mx25l. >> > Hm. I don't have any of those. > > There are times that it's disabled administratively as well, but that may > be on a per-I/O basis. > vfs.zfs.vol.unmap_enabled: 1 > This one doesn't seem to work. It looks like the only functionality it gates these days is DIOCGDELETE. > vfs.unmapped_buf_allowed: 1 > Well, this one works. Thanks for the tip. Unfortunately, it's a tunable, so I can't use it for any kind of automated testing. > > "Why do you ask?" is the next question... > > Warner > From owner-freebsd-hackers@freebsd.org Sun Dec 13 19:40:58 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 10D334C1D65 for ; Sun, 13 Dec 2020 19:40:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvFHs5Cn5z4pC2; Sun, 13 Dec 2020 19:40:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 0BDJeeQl069344 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 13 Dec 2020 21:40:43 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 0BDJeeQl069344 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 0BDJeeFs069343; Sun, 13 Dec 2020 21:40:40 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 13 Dec 2020 21:40:40 +0200 From: Konstantin Belousov To: Alan Somers Cc: Warner Losh , Ian Lepore , FreeBSD Hackers Subject: Re: char devices without SI_UNMAPPED? Message-ID: References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4CvFHs5Cn5z4pC2 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 19:40:58 -0000 On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: > > > > > > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > > > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: > >> > I'm trying to exercise the aio code that handles character devices > >> > that > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there any > >> > remaining character devices that don't allow unmapped I/O? > >> > > >> > -Alan > >> > > >> > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, > >> flash/mx25l. > >> > > > Hm. I don't have any of those. > > > > > > There are times that it's disabled administratively as well, but that may > > be on a per-I/O basis. > > vfs.zfs.vol.unmap_enabled: 1 > > > > This one doesn't seem to work. It looks like the only functionality it > gates these days is DIOCGDELETE. > > > > vfs.unmapped_buf_allowed: 1 > > > > Well, this one works. Thanks for the tip. Unfortunately, it's a tunable, > so I can't use it for any kind of automated testing. There is enough geoms which do not support unmapped bios, even if only in some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in sys/geom to see what I mean. After all, an option for geom_nop should be trivial, to force all bios to map, instead of inheriting from the lower provider. From owner-freebsd-hackers@freebsd.org Sun Dec 13 19:43:20 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7CD7C4C200D for ; Sun, 13 Dec 2020 19:43:20 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvFLc2wZYz4pKG for ; Sun, 13 Dec 2020 19:43:19 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x729.google.com with SMTP id i67so6255239qkf.11 for ; Sun, 13 Dec 2020 11:43:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Leym17MSasUK2v3VSsn3mdFaJKRsq3D9WOBNyFTzC3Q=; b=IVXUUYu5/f6KpWLS36lK+tbknQFdSG1IpiF/CALQTmhFyicurzlwfTGqTClYWhC5hC QR9MDZEGAUqg80qOh/v54m1u3rUPqfqZfg69Vgw7nx/D6WJtLO0/QnKHNWs3NZ/ihIPb IbzbYF7EBQKRYDGV/RS9TscztP80znZGzEFLMX9IpOGFeCKVvmb2Dw2vWSolc4CeiBiO R5S+3qFYxe78hd+F6lCYM9lurRWjXijWf72DCmEwzwE1tc6tyiRvfKwRSmHMr2PZC7ry ubel3OyOayEHVp3zjJR2RcA1bSwYRbgdrVu/SIEOleRA0nVQzkFQmIPli2oA0McoptQI D+gQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Leym17MSasUK2v3VSsn3mdFaJKRsq3D9WOBNyFTzC3Q=; b=SwKQQk/tTNOHCNK9CCDbyHmc2hG39j0El+DJ0OacjLYmay9mH0sibNEglwsOS4qfhv 85Nd2vW4OO6wEZfkywFx1jMTu9dRv4ACE87d7MJSF3ozb8VT+Cq/13XFCFV1sJ54Gsuq xGNW05DNoiyIQTXbFQgxMU+xrqJ9mMIpIGzgY2towhmTieQF9880n8LJxnUGEgKng4Ov b+fjNnwauKx7dyG1r1ALTg+6IKeZbwu8WcMvarMKA8A7keppxRy8zzVU2r5p6z+0dCh4 /ydYfnOn+PGSsatQoQ6iaEPAxxjnl6l1oU9nhjJ6F25x1R85jtkfZI8a7m4GHS+lF+RZ 00Kw== X-Gm-Message-State: AOAM530HdHp7j+yZdJqYMWtRRN5t3q1gQO4Ke6OQjK9oRdH62JUlX4yu /qtQR5zwsewPJy5pBFi+GTZABVZiVrFN15Cw6C2vdA== X-Google-Smtp-Source: ABdhPJx7KXaNEOqwGmVFH+Ekd/1vi2QX9Rsdw/RHL2e39slFYMTYsOmynMbbHBNJA4q1OQJY8okiVJ3QbFuvYBAawYQ= X-Received: by 2002:ae9:ebd5:: with SMTP id b204mr28913543qkg.195.1607888599139; Sun, 13 Dec 2020 11:43:19 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Warner Losh Date: Sun, 13 Dec 2020 12:43:08 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Konstantin Belousov Cc: Alan Somers , Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvFLc2wZYz4pKG X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 19:43:20 -0000 On Sun, Dec 13, 2020 at 12:40 PM Konstantin Belousov wrote: > On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: > > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: > > > > > > > > > > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > > > > > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: > > >> > I'm trying to exercise the aio code that handles character devices > > >> > that > > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there > any > > >> > remaining character devices that don't allow unmapped I/O? > > >> > > > >> > -Alan > > >> > > > >> > > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, > > >> flash/mx25l. > > >> > > > > > Hm. I don't have any of those. > > > > > > > > > > There are times that it's disabled administratively as well, but that > may > > > be on a per-I/O basis. > > > vfs.zfs.vol.unmap_enabled: 1 > > > > > > > This one doesn't seem to work. It looks like the only functionality it > > gates these days is DIOCGDELETE. > > > > > > > vfs.unmapped_buf_allowed: 1 > > > > > > > Well, this one works. Thanks for the tip. Unfortunately, it's a > tunable, > > so I can't use it for any kind of automated testing. > > There is enough geoms which do not support unmapped bios, even if only in > some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in sys/geom > to see what I mean. > > After all, an option for geom_nop should be trivial, to force all bios to > map, instead of inheriting from the lower provider. > There's also several CAM SIMs that don't set the PIM_UNMAPPED flag either: % grep -rl cam_sim_alloc . | wc 58 58 1378 % grep -lr PIM_UNMAPPED . | wc 28 28 658 Warner From owner-freebsd-hackers@freebsd.org Sun Dec 13 20:37:27 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A67F14C2D24 for ; Sun, 13 Dec 2020 20:37:27 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f171.google.com (mail-oi1-f171.google.com [209.85.167.171]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvGY34FSxz4rh5; Sun, 13 Dec 2020 20:37:27 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f171.google.com with SMTP id 15so16901750oix.8; Sun, 13 Dec 2020 12:37:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2txaVs2CEdy1Mjq/UpHQd5a22nguXMOlw0XE9zvfjD4=; b=Qyu5wZrISJywHQS6Pq9a7R3cl38m8Gppee/MW2nynWva3hqGHyuu3K8o/1Lt9CCUR/ o7wbiH31zD16cKqpk5n2MjPEGxIPvXcwv5R1AjbtoeSsUb+4LfFOMjprZ/9IWrMtZpud zLA5F/mZVFsGH3t3py755qVXg3CyUdH0LBTfKsi+q0F71iCLxFq6nw5DkiDPOYRqHDsS LeWQeCO/8yMzHxOYZh17wOiDxDb9G7pnangDFATCNEONim0ZPNzEMa8G4sPUqlMfCefF FKAZ9KHeNLoPqNa6Jk4M9jxIbTaEh1nnw7tGEAwlUpcIJQ4nBxrIhxZ1BEVN5GlEAjQD uQYA== X-Gm-Message-State: AOAM531y7gaLokt/SvPOOjs5uYE3irJlScgrfLyJn/I0FFGVdHyKWyS/ aenn/odTzDIQSmRbWxcqmtA5996c476m+yq3/648q4XO7pq/hA== X-Google-Smtp-Source: ABdhPJzXUoXjpGXwWbemPOisgfyFm1mJI1L1eLaLoDlGXhmYw3UVHNC5V+6zTUqLzkmu3uysguWlBcNXqk7k1z1iThc= X-Received: by 2002:aca:dd09:: with SMTP id u9mr15648566oig.73.1607891846562; Sun, 13 Dec 2020 12:37:26 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Alan Somers Date: Sun, 13 Dec 2020 13:37:15 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Konstantin Belousov Cc: Warner Losh , Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvGY34FSxz4rh5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 20:37:27 -0000 On Sun, Dec 13, 2020 at 12:40 PM Konstantin Belousov wrote: > On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: > > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: > > > > > > > > > > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: > > > > > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: > > >> > I'm trying to exercise the aio code that handles character devices > > >> > that > > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there > any > > >> > remaining character devices that don't allow unmapped I/O? > > >> > > > >> > -Alan > > >> > > > >> > > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, > > >> flash/mx25l. > > >> > > > > > Hm. I don't have any of those. > > > > > > > > > > There are times that it's disabled administratively as well, but that > may > > > be on a per-I/O basis. > > > vfs.zfs.vol.unmap_enabled: 1 > > > > > > > This one doesn't seem to work. It looks like the only functionality it > > gates these days is DIOCGDELETE. > > > > > > > vfs.unmapped_buf_allowed: 1 > > > > > > > Well, this one works. Thanks for the tip. Unfortunately, it's a > tunable, > > so I can't use it for any kind of automated testing. > > There is enough geoms which do not support unmapped bios, even if only in > some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in sys/geom > to see what I mean. > That's different. If a provider clears G_PF_ACCEPT_UNMAPPED, geom will create a transient mapping for any unmapped bios sent to that provider. But the provider still has SI_UNMAPPED set. SI_UNMAPPED is used in so few places, I'm wondering if it still has a purpose at all. Is it obsolete? > > After all, an option for geom_nop should be trivial, to force all bios to > map, instead of inheriting from the lower provider. > From owner-freebsd-hackers@freebsd.org Sun Dec 13 21:37:03 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 27EC24C4932 for ; Sun, 13 Dec 2020 21:37:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvHsq0R68z3Cfn for ; Sun, 13 Dec 2020 21:37:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x732.google.com with SMTP id h4so9073039qkk.4 for ; Sun, 13 Dec 2020 13:37:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=g2/mtZC3yfLAmX9XczVdT/a0PzKGA3HnxXiX1OGxRZ4=; b=dAXDclNiLOBhy0vODjh7XCQZeAVRIWw06+QeIO/nEkhY6aLq2G2IejnxbjOWWhazN3 Tj6jI1aJt191uj3+XPuD2vfPca0SRmgRm00N+uF/YytlaF0R3ebGpEdrzYsJH33h5fcP q37ERPnrRB+xN8o7CXhBBSuYGcCeleC4qajyHzYaSPvdRymo1GrWZ166wkEqtF+2KGL0 uM3bDFXhwxDc74pAwnqaMs2qjP/Va1oXZm72Gr2OooVCgzL6yYlqhoTa8R7cTXkELcBV diSpPn4Mpawvl7tyTmTRNfIsTB7NZeufkma/Od0G0m8d/O06syvaOyVjs0WixSxW0bAV PBcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=g2/mtZC3yfLAmX9XczVdT/a0PzKGA3HnxXiX1OGxRZ4=; b=earTeIs3mKnFVEeEq7zF+2Uj3+8oHqf3/+8pwISt2CxHkzugshQALsboQY+ZMNpz1Y 5DrD/tRfqoRZJYcfEULx2Omd8WM0TJLjV9sg8SITk+XRc7BloA8UgfAeosVURlEsZ5Gw BLJ2aE8yUfGiFwFkixuitAe1kbABjnXjdn+JTgzY9hpu5iup0f05VqJIAPfIXMA/3jao ZT0qIO1GzkGxAUvVT4NuzFxDCrE9r4lnstB16GcEXaMgkljmrGekdF9+Lr+tTKfMqgsQ NK62pOpdIBgAt0anonyGCHwTpsTo5Taol3IW+GURZ+K8hNgW5gXchoSkl5aUWtnUiw2K GUGA== X-Gm-Message-State: AOAM532A/SYcbot48NrtkGivtOxOosMLlTl0wo4sVKOEDd5/D76ciU31 5r2Z/YVQYPnAnhk5K7zmoQnpvr6+Q9ME2B1gZMRnzw== X-Google-Smtp-Source: ABdhPJyl+P9S1hPl8jD+KC3Jb+SwWB9mb7PewTiKNaqM0HSvWMmKvSGcW0q5zYBLhBJ3xYeQd7cI+MhIbs7vGEyoJSA= X-Received: by 2002:a37:4a4e:: with SMTP id x75mr18890129qka.89.1607895421947; Sun, 13 Dec 2020 13:37:01 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Warner Losh Date: Sun, 13 Dec 2020 14:36:51 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Alan Somers Cc: Konstantin Belousov , Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvHsq0R68z3Cfn X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 21:37:03 -0000 On Sun, Dec 13, 2020 at 1:37 PM Alan Somers wrote: > On Sun, Dec 13, 2020 at 12:40 PM Konstantin Belousov > wrote: > >> On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: >> > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: >> > >> > > >> > > >> > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: >> > > >> > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: >> > >> > I'm trying to exercise the aio code that handles character devices >> > >> > that >> > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there >> any >> > >> > remaining character devices that don't allow unmapped I/O? >> > >> > >> > >> > -Alan >> > >> > >> > >> >> > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, >> > >> flash/mx25l. >> > >> >> > > >> > Hm. I don't have any of those. >> > >> > >> > > >> > > There are times that it's disabled administratively as well, but that >> may >> > > be on a per-I/O basis. >> > > vfs.zfs.vol.unmap_enabled: 1 >> > > >> > >> > This one doesn't seem to work. It looks like the only functionality it >> > gates these days is DIOCGDELETE. >> > >> > >> > > vfs.unmapped_buf_allowed: 1 >> > > >> > >> > Well, this one works. Thanks for the tip. Unfortunately, it's a >> tunable, >> > so I can't use it for any kind of automated testing. >> >> There is enough geoms which do not support unmapped bios, even if only in >> some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in >> sys/geom >> to see what I mean. >> > > That's different. If a provider clears G_PF_ACCEPT_UNMAPPED, geom will > create a transient mapping for any unmapped bios sent to that provider. > But the provider still has SI_UNMAPPED set. SI_UNMAPPED is used in so few > places, I'm wondering if it still has a purpose at all. Is it obsolete? > It looks like none of the devices in the tree set it, except the goem namespace, the sa CAM device and the geom disk devices. This leaves plenty of other devices in the tree that use physio() that aren't marked: pt, zvol, altera avgen, altera sd card, amr, cfi, firewire, a bunch of different flash devices, mfi, mlx, pst, and twe. None of these drivers have been converted over to grok unmapped I/O, which is a relatively new feature. Now, some of these devices might have a good case made for obsoleting, but they aren't there yet... What makes you think this is obsolete? Warner > >> After all, an option for geom_nop should be trivial, to force all bios to >> map, instead of inheriting from the lower provider. >> > From owner-freebsd-hackers@freebsd.org Sun Dec 13 22:06:52 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 172654C52B2 for ; Sun, 13 Dec 2020 22:06:52 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvJXC7109z3FB2; Sun, 13 Dec 2020 22:06:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f51.google.com with SMTP id h18so13923579otq.12; Sun, 13 Dec 2020 14:06:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ziGMNRr73f0i18k58zE2IQMm52yiMOl3TGbj5G7yA8A=; b=EQfND+Y2qGdwcsVMTEKdo7/XMfShz5xoFIdbMYzB1IHuyTrnlaJbqP7kwtYWYEYwD8 h3aftGF/sSY/BQ7ub5Rr/PgXyCP1ELU1uf3mqSdHEfoke60QjxDbhwFVzx3l3xvbTk2j pklFoiFFhm1X0RnFIOg+EDjAxV7VLpcXh6MpdrZjUOGsWBKnyK1vMXvO+wm/HoCSx/qE p3Y+CR57uPOIZFPOBri1AZUGRz11LX+LufwyRr3h0mEZwsv/iRO9EgLJNOgSbVGBDH5A qisQ/RtYOnMIFAxJABzfv8NzcwCfGPaxfvBzfM4a3R0SsRGuWl2R0RT2lwviZV6BZH2h QeEA== X-Gm-Message-State: AOAM530vBTHzgr308bh9G3PLieJmctqT0ZNmjdBOhYkqo189Oqckg1y3 K+oJ0l2Fzx6Jtv62QlosHMhGr+m1wQQUF/oCApk= X-Google-Smtp-Source: ABdhPJzyOXpGQKqPlUvLfsqPI9+ep8Ku/iUdEBCRfjqXhuiLIi9075HBHNCx2VlYzB6jpKd0kZP9b/YovxnIhqDlL4o= X-Received: by 2002:a05:6830:30a8:: with SMTP id g8mr11790066ots.291.1607897210678; Sun, 13 Dec 2020 14:06:50 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Alan Somers Date: Sun, 13 Dec 2020 15:06:39 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? To: Warner Losh Cc: Konstantin Belousov , Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvJXC7109z3FB2 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 22:06:52 -0000 On Sun, Dec 13, 2020 at 2:37 PM Warner Losh wrote: > > > On Sun, Dec 13, 2020 at 1:37 PM Alan Somers wrote: > >> On Sun, Dec 13, 2020 at 12:40 PM Konstantin Belousov >> wrote: >> >>> On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: >>> > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: >>> > >>> > > >>> > > >>> > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore wrote: >>> > > >>> > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: >>> > >> > I'm trying to exercise the aio code that handles character devices >>> > >> > that >>> > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are there >>> any >>> > >> > remaining character devices that don't allow unmapped I/O? >>> > >> > >>> > >> > -Alan >>> > >> > >>> > >> >>> > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, >>> > >> flash/mx25l. >>> > >> >>> > > >>> > Hm. I don't have any of those. >>> > >>> > >>> > > >>> > > There are times that it's disabled administratively as well, but >>> that may >>> > > be on a per-I/O basis. >>> > > vfs.zfs.vol.unmap_enabled: 1 >>> > > >>> > >>> > This one doesn't seem to work. It looks like the only functionality it >>> > gates these days is DIOCGDELETE. >>> > >>> > >>> > > vfs.unmapped_buf_allowed: 1 >>> > > >>> > >>> > Well, this one works. Thanks for the tip. Unfortunately, it's a >>> tunable, >>> > so I can't use it for any kind of automated testing. >>> >>> There is enough geoms which do not support unmapped bios, even if only in >>> some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in >>> sys/geom >>> to see what I mean. >>> >> >> That's different. If a provider clears G_PF_ACCEPT_UNMAPPED, geom will >> create a transient mapping for any unmapped bios sent to that provider. >> But the provider still has SI_UNMAPPED set. SI_UNMAPPED is used in so few >> places, I'm wondering if it still has a purpose at all. Is it obsolete? >> > > It looks like none of the devices in the tree set it, except the goem > namespace, the sa CAM device and the geom disk devices. This leaves plenty > of other devices in the tree that use physio() that aren't marked: pt, > zvol, altera avgen, altera sd card, amr, cfi, firewire, a bunch of > different flash devices, mfi, mlx, pst, and twe. > I previously tested zvol and saw that it had SI_UNMAPPED set. But that was with vfs.zfs.vol.mode=1. With 2, I see that it no longer sets SI_UNMAPPED. > None of these drivers have been converted over to grok unmapped I/O, which > is a relatively new feature. Now, some of these devices might have a good > case made for obsoleting, but they aren't there yet... What makes you think > this is obsolete? > Just because so few places check it (2), and it was set by all geom devices. It smelled like the kind of thing that might've been leftover from before some critical refactor. But I guess I was wrong. > > Warner > > >> >>> After all, an option for geom_nop should be trivial, to force all bios to >>> map, instead of inheriting from the lower provider. >>> >> From owner-freebsd-hackers@freebsd.org Sun Dec 13 23:33:56 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 42C014C7B82 for ; Sun, 13 Dec 2020 23:33:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CvLSg3Kw8z3PHY for ; Sun, 13 Dec 2020 23:33:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-ot1-f44.google.com with SMTP id b18so14077503ots.0 for ; Sun, 13 Dec 2020 15:33:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=RoEUineAu9lMg3aTPtDqW6we0E9iwm1BqbQU41B/ePI=; b=Q5CzkZoJHnwfg9/5FcWOL7MiSP+p4/CADwudb5qxFaatiwlLA77t6dASEw5YZRA3P7 L447xaXL7lzpyl6YXveP+mGEXUtB36t57+9UbIKi27xzDBlisrpbGgJ0TeyfpBh5mRGg q/n/rK4ySies51k4Pbq9wr3Pma8xND+5t0Shtzb0Vfo8M/NroTRsAGLGZxl62aH//jq6 QEtFFu6xCPJKOcv4n3Xzf/gNL3mjbdu0r7IYmgOzOLxXjuSopqazfcpRkkO9dues9EUo 1fHHxQoDBjkaAzzxFEAyen9eZi+tcvTBor0yapCH+XS7d5POT3Op4eQbf3ZJQSTnfHAK 3Qmg== X-Gm-Message-State: AOAM532bh9EmKKUWXx5A/acex8gFc4Qw8PflpgJp1vD7/aV0ZUETQ8+0 2CLV5bnobwuKBLu/NGckR077c/YJDgHWoBGN6qU= X-Received: by 2002:a05:6830:30a8:: with SMTP id g8mt12245295ots.291.1607902434261; Sun, 13 Dec 2020 15:33:54 -0800 (PST) MIME-Version: 1.0 References: <6dd927984d69ef0e95e1e90651bcd8087bc4eec4.camel@freebsd.org> In-Reply-To: From: Alan Somers Date: Sun, 13 Dec 2020 16:33:43 -0700 Message-ID: Subject: Re: char devices without SI_UNMAPPED? Cc: Warner Losh , Konstantin Belousov , Ian Lepore , FreeBSD Hackers X-Rspamd-Queue-Id: 4CvLSg3Kw8z3PHY X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.210.44 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [0.08 / 15.00]; RCVD_TLS_ALL(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[209.85.210.44:from]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.923]; MISSING_TO(2.00)[]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[209.85.210.44:from]; FREEFALL_USER(0.00)[asomers]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; SPAMHAUS_ZRD(0.00)[209.85.210.44:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[209.85.210.44:from]; FREEMAIL_CC(0.00)[bsdimp.com,gmail.com,freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2020 23:33:56 -0000 On Sun, Dec 13, 2020 at 3:06 PM Alan Somers wrote: > On Sun, Dec 13, 2020 at 2:37 PM Warner Losh wrote: > >> >> >> On Sun, Dec 13, 2020 at 1:37 PM Alan Somers wrote: >> >>> On Sun, Dec 13, 2020 at 12:40 PM Konstantin Belousov < >>> kostikbel@gmail.com> wrote: >>> >>>> On Sun, Dec 13, 2020 at 12:20:49PM -0700, Alan Somers wrote: >>>> > On Sun, Dec 13, 2020 at 11:20 AM Warner Losh wrote: >>>> > >>>> > > >>>> > > >>>> > > On Sun, Dec 13, 2020 at 11:18 AM Ian Lepore >>>> wrote: >>>> > > >>>> > >> On Sun, 2020-12-13 at 10:27 -0700, alan somers wrote: >>>> > >> > I'm trying to exercise the aio code that handles character >>>> devices >>>> > >> > that >>>> > >> > don't set the SI_UNMAPPED flag. But I can't find any. Are >>>> there any >>>> > >> > remaining character devices that don't allow unmapped I/O? >>>> > >> > >>>> > >> > -Alan >>>> > >> > >>>> > >> >>>> > >> I assume you mean disk-like devices? Probably mmcsd, flash/at45d, >>>> > >> flash/mx25l. >>>> > >> >>>> > > >>>> > Hm. I don't have any of those. >>>> > >>>> > >>>> > > >>>> > > There are times that it's disabled administratively as well, but >>>> that may >>>> > > be on a per-I/O basis. >>>> > > vfs.zfs.vol.unmap_enabled: 1 >>>> > > >>>> > >>>> > This one doesn't seem to work. It looks like the only functionality >>>> it >>>> > gates these days is DIOCGDELETE. >>>> > >>>> > >>>> > > vfs.unmapped_buf_allowed: 1 >>>> > > >>>> > >>>> > Well, this one works. Thanks for the tip. Unfortunately, it's a >>>> tunable, >>>> > so I can't use it for any kind of automated testing. >>>> >>>> There is enough geoms which do not support unmapped bios, even if only >>>> in >>>> some configurations. Recursively grep for G_PF_ACCEPT_UNMAPPED in >>>> sys/geom >>>> to see what I mean. >>>> >>> >>> That's different. If a provider clears G_PF_ACCEPT_UNMAPPED, geom will >>> create a transient mapping for any unmapped bios sent to that provider. >>> But the provider still has SI_UNMAPPED set. SI_UNMAPPED is used in so few >>> places, I'm wondering if it still has a purpose at all. Is it obsolete? >>> >> >> It looks like none of the devices in the tree set it, except the goem >> namespace, the sa CAM device and the geom disk devices. This leaves plenty >> of other devices in the tree that use physio() that aren't marked: pt, >> zvol, altera avgen, altera sd card, amr, cfi, firewire, a bunch of >> different flash devices, mfi, mlx, pst, and twe. >> > > I previously tested zvol and saw that it had SI_UNMAPPED set. But that > was with vfs.zfs.vol.mode=1. With 2, I see that it no longer sets > SI_UNMAPPED. > Oh, and it turns out that there's bug with the ZFS volmode property that also interferes with this test. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251828 . > > >> None of these drivers have been converted over to grok unmapped I/O, >> which is a relatively new feature. Now, some of these devices might have a >> good case made for obsoleting, but they aren't there yet... What makes you >> think this is obsolete? >> > > Just because so few places check it (2), and it was set by all geom > devices. It smelled like the kind of thing that might've been leftover > from before some critical refactor. But I guess I was wrong. > > >> >> Warner >> >> >>> >>>> After all, an option for geom_nop should be trivial, to force all bios >>>> to >>>> map, instead of inheriting from the lower provider. >>>> >>> From owner-freebsd-hackers@freebsd.org Tue Dec 15 14:00:32 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3F01D4B6FAB for ; Tue, 15 Dec 2020 14:00:32 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CwKf80VNZz3tHN for ; Tue, 15 Dec 2020 14:00:32 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.nyi.freebsd.org (Postfix) id 10E434B6FAA; Tue, 15 Dec 2020 14:00:32 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 10B024B70A8 for ; Tue, 15 Dec 2020 14:00:32 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwKf71TTdz3tN3 for ; Tue, 15 Dec 2020 14:00:30 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 141658A3C7 for ; Tue, 15 Dec 2020 14:00:23 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.16.1/8.16.1) with ESMTPS id 0BFE0MIw025471 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 15 Dec 2020 14:00:22 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 0BFE0Mpv025470; Tue, 15 Dec 2020 14:00:22 GMT (envelope-from phk) To: hackers@freebsd.org Subject: Should/does loader.efi respect the "bootme" GPT attribute ? From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25468.1608040822.1@critter.freebsd.dk> Date: Tue, 15 Dec 2020 14:00:22 +0000 Message-ID: <25469.1608040822@critter.freebsd.dk> X-Rspamd-Queue-Id: 4CwKf71TTdz3tN3 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk X-Spamd-Result: default: False [-0.93 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[130.225.244.222:from]; NEURAL_SPAM_SHORT(0.07)[0.071]; FREEFALL_USER(0.00)[phk]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[130.225.244.222:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_NA(0.00)[freebsd.dk]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; MAILMAN_DEST(0.00)[hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 14:00:32 -0000 It looks to me like the GPT attributes "bootme", "bootonce" and "bootfailed" are unknown to loader.efi ? Is this intentional or should it be fixed ? -- 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-hackers@freebsd.org Tue Dec 15 14:53:42 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 09F604B8A90 for ; Tue, 15 Dec 2020 14:53:42 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CwLqT5tMlz4Rby for ; Tue, 15 Dec 2020 14:53:41 +0000 (UTC) (envelope-from janm@transactionware.com) Received: by mailman.nyi.freebsd.org (Postfix) id C9D424B8C12; Tue, 15 Dec 2020 14:53:41 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C99DF4B8867 for ; Tue, 15 Dec 2020 14:53:41 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 4CwLqT0dh6z4RSZ for ; Tue, 15 Dec 2020 14:53:39 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 69297 invoked by uid 907); 15 Dec 2020 14:53:31 -0000 Received: from p5dd141db.dip0.t-ipconnect.de (HELO [192.168.7.19]) (93.209.65.219) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Wed, 16 Dec 2020 01:53:31 +1100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\)) Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? From: Jan Martin Mikkelsen In-Reply-To: <25469.1608040822@critter.freebsd.dk> Date: Tue, 15 Dec 2020 15:53:25 +0100 Cc: hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <25469.1608040822@critter.freebsd.dk> To: Poul-Henning Kamp X-Mailer: Apple Mail (2.3654.20.0.2.21) X-Rspamd-Queue-Id: 4CwLqT0dh6z4RSZ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 14:53:42 -0000 I=E2=80=99m installing gptboot.efi into the EFI boot partition and using = that to use the GPT attributes. Is there an extra benefit to using loader.efi? Regards, Jan M. > On 15 Dec 2020, at 15:00, Poul-Henning Kamp = wrote: >=20 > It looks to me like the GPT attributes "bootme", "bootonce" and = "bootfailed" > are unknown to loader.efi ? >=20 > Is this intentional or should it be fixed ? >=20 > --=20 > 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. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Tue Dec 15 15:58:41 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 715C14BA71A for ; Tue, 15 Dec 2020 15:58:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CwNGT1jr2z4WxS for ; Tue, 15 Dec 2020 15:58:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.nyi.freebsd.org (Postfix) id 3AE014BA5F6; Tue, 15 Dec 2020 15:58:41 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3AA834BA883 for ; Tue, 15 Dec 2020 15:58:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwNGT131Lz4X2d for ; Tue, 15 Dec 2020 15:58:40 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf2c.google.com with SMTP id u16so9758034qvl.7 for ; Tue, 15 Dec 2020 07:58:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OMnTqPUarO1MtCaZcngFSkohSlEWrvZyHltsKcuAc/Y=; b=0eomBi/jX3L6O0VS2wki4Yv6Mt3XcfwGmD57PgpFw92WLDCohjS63KoVbRoAmqE+j0 Oo+DhElwq3rLxlljzg71xBC7492JOLpmMVmoydHB4hE+MCoSGXr8z0An7/LhWWLtlGFb 0vK7phsKxe/WBTGPstuFDaqBh6uF9HM3clD0z03/FeTmFUJksIea+7pmjNeU2wxp48Mw GXdJEZb+2IEoUf39901ywUQtkfdX6+2ymf168hPp7Xa1K9PWE4t1+OIlZ8+V2vkQPD0L EA5ILzNs0LQlGDQW8YIsfjY/EJEQJrkB2zIgdtO04UxpJPgMXFzQomS1pWV+oetibdjF PyGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OMnTqPUarO1MtCaZcngFSkohSlEWrvZyHltsKcuAc/Y=; b=WpQQwDp3gX0ifOmHoYebjPd9DHlzof9q+GsmfdDwZraxZuahb6Faf4BU8ikRMTo7ua SE3FP9MKHfRkt2SzgUC9xydy2Ak2kwcwrujS3NNgLF8LhfvAJ96/WjwDcRMSII9GCNS6 Ov/y5+zWcIEPFroxFa5Tkfc86Wqy2Un/R71xFoQ/G3OOe2A5CMyQQQX/hV2mtFzKZF70 Z6QZ3StPKdzYfepUY4eLkCRYV2tQpOnCAeRbVZwT9R+wR008kyui55Yy0sLjybc8qsss jQgBtQ1I1s12f8uKTLN3NzVjNG8s04QqRdvD1DgFnda9/0q3MHWGy54Hru7Py3REGGcl Gfow== X-Gm-Message-State: AOAM530j5KJBG3vHHR2o9ohQTisWYzf5tePds9dcHm/3pW2kmDeDWHLT 701RGU2AQeyH/59ZgYK5MZO0/rY9otCLKNuiP/K5aVhV81xSGw== X-Google-Smtp-Source: ABdhPJyoyWHuvBoqwzCG6PffDZoFU7D3MHrEJ80DNopr+0xIQnKUWPMvE6rjahWqqp4ldkDWvW6KBjnc0FQ+b8DC3o4= X-Received: by 2002:a0c:bf0f:: with SMTP id m15mr38173133qvi.23.1608047919959; Tue, 15 Dec 2020 07:58:39 -0800 (PST) MIME-Version: 1.0 References: <25469.1608040822@critter.freebsd.dk> In-Reply-To: <25469.1608040822@critter.freebsd.dk> From: Warner Losh Date: Tue, 15 Dec 2020 08:58:29 -0700 Message-ID: Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? To: Poul-Henning Kamp Cc: "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: 4CwNGT131Lz4X2d X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 15:58:41 -0000 On Tue, Dec 15, 2020 at 7:00 AM Poul-Henning Kamp wrote: > It looks to me like the GPT attributes "bootme", "bootonce" and > "bootfailed" > are unknown to loader.efi ? > BIOS "loader" doesn't respect these flags either. That's done by gptboot. The equivalent in UEFI land is gptboot.efi. > Is this intentional or should it be fixed ? > It is intentional. UEFI really doesn't want you using non-standard partition flags to determine boot order. We provide a way to do it with gptboot.efi, but UEFI makes it hard to support. loader.efi is kinda late in the process anyway, and it's main loop makes supporting gptboot-like functionality hard due to the way things are ordered and how gptboot rewrites the GPT partition table at different points in the boot. UEFI has its own bootnext protocol, that works in conjunction with the EFI environment variables to have a more robust, less 'guess what I mean' approach. So all in all, it's hard, non-standard and doesn't play well with UEFI. I wrote gptboot.efi for USB sticks where we have two systems installed that travel from system to system. It's a bit hacky, but I needed something that worked in a mixed UEFI and BIOS environment that was in place at our system integrators. There's some times you gotta not play well, but this won't work everywhere :) Warner From owner-freebsd-hackers@freebsd.org Tue Dec 15 16:51:45 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E45614BBB95 for ; Tue, 15 Dec 2020 16:51:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CwPRj5Nhcz4Zj3 for ; Tue, 15 Dec 2020 16:51:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.nyi.freebsd.org (Postfix) id B8EF04BBB94; Tue, 15 Dec 2020 16:51:45 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B8B794BBAC2 for ; Tue, 15 Dec 2020 16:51:45 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwPRj451zz4ZnX for ; Tue, 15 Dec 2020 16:51:44 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id DACE78A3C7; Tue, 15 Dec 2020 16:51:42 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.16.1/8.16.1) with ESMTPS id 0BFGpg86026113 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 15 Dec 2020 16:51:42 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 0BFGpfrF026112; Tue, 15 Dec 2020 16:51:41 GMT (envelope-from phk) To: Warner Losh cc: "freebsd-hackers@freebsd.org" Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? In-reply-to: From: "Poul-Henning Kamp" References: <25469.1608040822@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <26110.1608051101.1@critter.freebsd.dk> Date: Tue, 15 Dec 2020 16:51:41 +0000 Message-ID: <26111.1608051101@critter.freebsd.dk> X-Rspamd-Queue-Id: 4CwPRj451zz4ZnX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 16:51:45 -0000 -------- Warner Losh writes: > It is intentional. UEFI really doesn't want you using non-standard > partition flags to determine boot order. So how would one go about doing "boot0/nanobsd-style" dual root the "proper" way in an UEFI environment ? -- 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-hackers@freebsd.org Tue Dec 15 00:00:03 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 357934CB08C; Tue, 15 Dec 2020 00:00:03 +0000 (UTC) (envelope-from owner-freebsd-quarterly-calls@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4Cvz0L3YgGz4YBs; Tue, 15 Dec 2020 00:00:02 +0000 (UTC) (envelope-from owner-freebsd-quarterly-calls@freebsd.org) Delivered-To: freebsd-quarterly-calls@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4994B4CAE92; Tue, 15 Dec 2020 00:00:01 +0000 (UTC) (envelope-from debdrup@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cvz0K0s8Fz4YXy; Tue, 15 Dec 2020 00:00:01 +0000 (UTC) (envelope-from debdrup@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1607990401; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=CzE01EMmyg3K6KfTxm5h+D5DiJ4K0uwdj8hfSlDUdAE=; b=b0wh8q5lbILjqOiribtOVXwi+TvQ9LVESY/2homHfbV3hNpdPD0xUREgPXCX4wJb/t+Zow DoK9QEHhxunI1AGuklB32SxU9GNmhX52ETcvVVclloynACDbo5AqflXp616TOi4/HidI0r Pj498heih0Quml5SlFcErfB3AdS/Y1N0Apelqt38td1FoSbGDXMYTut6p/HAAK+JDdF4It QicvhSLIrn8o0pqo8VI3N6EsQoQH6teDewAAs/3l2l+VkOUATZK9r8W529ppsLgADoB1Mj 1nfyDV/JYmzZurUESuk4cz2pe0QUBkm8pey93Mty1nob12QpfcPWkCByEOuWtA== Received: by freefall.freebsd.org (Postfix, from userid 1471) id 0789B8266; Tue, 15 Dec 2020 00:00:00 +0000 (UTC) To: freebsd-quarterly-calls@FreeBSD.org Subject: [2 WEEKS LEFT REMINDER] Call for 2020Q4 quarterly status reports Message-Id: <20201215000001.0789B8266@freefall.freebsd.org> Date: Tue, 15 Dec 2020 00:00:00 +0000 (UTC) From: Daniel Ebdrup Jensen ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1607990401; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc; bh=CzE01EMmyg3K6KfTxm5h+D5DiJ4K0uwdj8hfSlDUdAE=; b=D8WvGlA+J0Do90cE+lJoQx4zlNO03dRStmRhQH62ETVQXQzkoQYWsQP8e8WHIxxkv+iyNC v9EwSQYE0yACElQeUzBAP3ZPiaxcdvb883aowloAp9DnrokvnJbLd35HYmDdihsOeWd/S5 Km9OhjiW8GVFywMWE69cdA+WRkB8x053Y6ccdcbVad/ZLaLyG5rag9MkmEF3Wdf2WirTmP Zx2KAYluwchzXonYZk1A4NJ7XU2VWcZURWQGtQBC79luWQUHPsV90o/3fq74n/jjTDoxrK QNDrHJWGLDNqP3MSnTdRB2gYq6UrkIvkntp+xL5nOYVNhtxb74dhR2ewt6Nl7g== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1607990401; a=rsa-sha256; cv=none; b=JLOOJO8o2Mdddh6WPOWNR+gc9D1kGH5FoPSN8Cd97jU5ZflQdAcUrHUfBHpKEUpxg1hGky JR+jeSsKJiiaFSXUsf1sM+xGOUUq6RQ24HtxYMhiXgpl7GMhvHKgrWD718xPd34QId962T 3cRZ6h2hu7g5sfJHbYx15SjvXS1A7vVuiwzGXF9c0dFwHXVRn+6Up6mEyrPVeibVnhRT+Z 8kwGYroMODMBX2+JxS8px8sOHFDPryLlWfWnQZcgSg762lF8X36BVaSYT6A1bBdgnqcu7t n4yNnM73ab/CV0ZbB7qjlz3YjJv3pUKZAqKx1zj9OBPAbqiFjy4D5/26e8v5XA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: freebsd-quarterly-calls@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: owner-freebsd-quarterly-calls@freebsd.org Sender: owner-freebsd-quarterly-calls@freebsd.org X-Mailman-Approved-At: Tue, 15 Dec 2020 18:36:53 +0000 X-BeenThere: freebsd-hackers@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 00:00:03 -0000 Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2021 for work done since the last round of Quarterly Reports: October 2020 - December 2020. I would like to remind you that reports are collected during the last month of every quarter. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and they provide a great way to inform FreeBSD users and developers about work that is underway or has been completed. Report submissions are not limited to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred method is to follow the guidelines at the Quarterly GitHub repository: https://github.com/freebsd/freebsd-quarterly Alternatively you can fetch the Markdown template, fill it in, and email it to quarterly-submissions@FreeBSD.org. The template can be found at: https://raw.githubusercontent.com/freebsd/freebsd-quarterly/master/report-sample.md We look forward to seeing your 2020Q4 reports! Thanks, Daniel Ebdrup Jensen (on behalf of quarterly@) _______________________________________________ freebsd-quarterly-calls@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-quarterly-calls To unsubscribe, send any mail to "freebsd-quarterly-calls-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Tue Dec 15 20:10:38 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 693274C0D5F for ; Tue, 15 Dec 2020 20:10:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CwTsB0tcXz4pG9 for ; Tue, 15 Dec 2020 20:10:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.nyi.freebsd.org (Postfix) id 1E5154C0E77; Tue, 15 Dec 2020 20:10:38 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1E16F4C0E76 for ; Tue, 15 Dec 2020 20:10:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwTsB0DDmz4pM4 for ; Tue, 15 Dec 2020 20:10:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x733.google.com with SMTP id 186so20437571qkj.3 for ; Tue, 15 Dec 2020 12:10:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SIbKdE9psCSI8ezjEr3CwYwqSOmZRikekqaeOblGKb4=; b=TfGbfvlVD/Mqj7T5mE1pyVSD4DaqlMnKAGC9GXPRJ60pqDcyz9FP4LIDiFrJW80mK8 St8lBmlJJG18Nca6G8DHwv6hFJHFYnunw1CEIIupoeJeOW9Kjhp5zNnzqh5QH8cMdtgu npS2Z0AU4wwfuJ/YerPi8NM3CtAJH2YKf6uKUCSlXEe6kW5EQaaKGI1+stAWLfN2Tq07 H4x046yuOgmMORQq0KuNoVvm4zHNS0AptPY2hXxBVfjY2tbrBPOfaMalhDwgpIBdjLgl 9zn8ZilCtoBStksYbmaR7ptHNrN5bql4aa7hEF35ZH131fKknlQ9OKLHpQxIBfiTI6Db xTkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SIbKdE9psCSI8ezjEr3CwYwqSOmZRikekqaeOblGKb4=; b=jeNnlbp5KnsrpDxtuqrYxR5PK9Q2eh0gKMnHHV1nGhRBKbFvvoYjdaifcZZxZAwuoj rX59osdTmRvXMx+ShweoOoBhBy0hC9diwBuYJYb4om/je4y1X4ZPKbtXzpkizVpqqhzd LYlRo3PGBoRFJJ5xEjFjpBWMZbtlb8WTNdtbIUKuUA7BQfQvZ/58xpOmCYx/IFsBleiE CSunEmnaml+fdXVP2Qw4OW8T0bZNmPK3Yvg0P5OkBY52fzpUByCjpeEockOrlZl/vD8l +8BQ2F30352rNbDQwj2mugAos0V4CV6Z/Fb7/K0PBfqfVhNGIcQJ+yHJnKMVNHfNYsI/ i48w== X-Gm-Message-State: AOAM532qWy+uVKz6JJa2EJrqvZQaZPSd/nveXaFOPQudRL+crfycUjnS O61ADCVWPV12gcEHvoWmjdUjb5+uhwhvnEWihpvILShJ2Bzg0w== X-Google-Smtp-Source: ABdhPJx/Ga6PxdZJiP8+PVuQ9z+ce5Vd/2Wp0DfqE+FyYP3hZZplBI7C7MEtHnuzQ/YI0F3hE0SlxA9Sv3SZUGHc4vw= X-Received: by 2002:a37:306:: with SMTP id 6mr20005265qkd.206.1608063036376; Tue, 15 Dec 2020 12:10:36 -0800 (PST) MIME-Version: 1.0 References: <25469.1608040822@critter.freebsd.dk> <26111.1608051101@critter.freebsd.dk> In-Reply-To: <26111.1608051101@critter.freebsd.dk> From: Warner Losh Date: Tue, 15 Dec 2020 13:10:25 -0700 Message-ID: Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? To: Poul-Henning Kamp Cc: "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: 4CwTsB0DDmz4pM4 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2020 20:10:38 -0000 On Tue, Dec 15, 2020 at 9:51 AM Poul-Henning Kamp wrote: > -------- > Warner Losh writes: > > > It is intentional. UEFI really doesn't want you using non-standard > > partition flags to determine boot order. > > So how would one go about doing "boot0/nanobsd-style" dual > root the "proper" way in an UEFI environment ? > By using gptboot.efi in the ESP and placaing loader.efi in the UFS partitions... Warner From owner-freebsd-hackers@freebsd.org Wed Dec 16 10:04:06 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EBFDE4B6ADE; Wed, 16 Dec 2020 10:04:06 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwrLt2Bs2z4h02; Wed, 16 Dec 2020 10:04:06 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-ot1-x334.google.com with SMTP id a109so22346564otc.1; Wed, 16 Dec 2020 02:04:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=KxZIKbCYPpmECpPoFUpQg2mEei1paeLRmIb0qbw2NHM=; b=KiDsCfR5r7BNs4Q9C74PXmgTz2LL/b2sirHgEAxtMEQ1YuC6hEY30SG6IeF16p5+lU sioIeuF0PuvA8nNbVoj3V7IJDfbz1Q/+3Kw293j6EVqvNmns9oKy+lhutabaEeJ7b7Le kqdzKY+Ko9bfa+6+XdHxPaxXyU8Hu4qtamkevmrvq6C/RFjC9CFKpifOhipXa63ZKwSh LEEEbh8edzPhRTKWKm5ZwJR3l/RUDTeMgoN4ASLcTzSNhbHmoMFjvKPRwQdyVZfqhwld ceB8LeKGQeir33s/uUZ56SkD/miKVTx3eUuEqeqP+z4FVqNXffUUOF4DDDYYjOiE6CPE 93Iw== 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=KxZIKbCYPpmECpPoFUpQg2mEei1paeLRmIb0qbw2NHM=; b=lDU61MrnSHj3qIUssnaOhNyrpWdlHwddNqpeeUtGvsP23YDr3jgkXCWtcVGyJ72lfJ W1TXFFzJ6soOn/iiJRIEKeZzTCW8Go/1femIxlX9ID5rOIL2WlZwKRSMSl9arXAN8Ui1 +ruHAO5MbLAYe/iusOZ76Azk2K2Gd1qer3lc8aVK8DkOM4BezwPtjT1+5zaOFQDIpJ/T b482ISH8QrLIS1Goh2CxA37Ub9k4TUf03bY77JVNpOk/xPkc3986DuyTq6NamalI0X4a LI3Q4gQuGFHdjy4AutRhVCNgN4G/YBSECK5fHmPO4HZK1wjAMGK95tIxoBEhBbVI+xor naFg== X-Gm-Message-State: AOAM5310WavtOunDMV7feDxwdd+qNTidFelcS47bE5n1BGvRVCyIcWNu XZCV0vTyHlVdqabWLYAeanRFEYwK4e7TTBiBO5XF1N1Oo4k= X-Google-Smtp-Source: ABdhPJwbEHep9c/LciyuEL/+6yhzydXigYqZVvzwGPfYoAkzOCfsKDkDb3NQjoB4LXTpNqbAcHCsMnHZyTu6sub9YMM= X-Received: by 2002:a9d:453:: with SMTP id 77mr18295069otc.91.1608113044461; Wed, 16 Dec 2020 02:04:04 -0800 (PST) MIME-Version: 1.0 From: Rajesh Kumar Date: Wed, 16 Dec 2020 15:33:53 +0530 Message-ID: Subject: Netmap Library not getting installed on custom kernel installation To: freebsd-net@freebsd.org, FreeBSD Hackers X-Rspamd-Queue-Id: 4CwrLt2Bs2z4h02 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=KiDsCfR5; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rajfbsd@gmail.com designates 2607:f8b0:4864:20::334 as permitted sender) smtp.mailfrom=rajfbsd@gmail.com X-Spamd-Result: default: False [-2.03 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::334:from]; NEURAL_SPAM_SHORT(0.97)[0.968]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::334:from:127.0.2.255]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::334:from]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-net,freebsd-hackers]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 10:04:07 -0000 Hi, I am trying to compile the netmap tools(pkt-gen, bridge etc.,) and getting the below error. */root//freebsd/tools/tools/netmap/pkt-gen.c:47:10: fatal error: 'libnetmap.h' file not found#include ^~~~~~~~~~~~~1 error generated.*** Error code 1* On debug, I don't see the libnetmap.h file getting installed in the /usr/obj/ directory. Whereas, in another similar machine I have the file in /usr/obj and compilation of netmap tools goes fine. For the test, I just copied libnetmap.h from the source and it leads to linker error. So seems the libnetmap library is not installed properly. I installed a custom kernel just disabling the debug options with the FreeBSD-CURRENT branch. After rebooting to the custom kernel, I tried to compile the netmap tools (with some changes) and ran into the above error. How to get the netmap tools compiled in this scenario? Am i missing something? From owner-freebsd-hackers@freebsd.org Wed Dec 16 13:42:31 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5B32B4BD393; Wed, 16 Dec 2020 13:42:31 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwxBt6ZFLz4vT7; Wed, 16 Dec 2020 13:42:30 +0000 (UTC) (envelope-from rajfbsd@gmail.com) Received: by mail-oi1-x22b.google.com with SMTP id d203so6321322oia.0; Wed, 16 Dec 2020 05:42:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=JKd/c1e9MQ+nWPR0mewY90955nZJz0S21qiaRcGcGZk=; b=ULWit7Kr3XqewYDA6J9KvdPXShV1quiSMj80aG9Ty5WUYopAsiSgnh2SF0PXfPSET9 VHho+0c6G4TmoyVaZ2NVYn0oIc8Om++Wu5TVS1Trzl3l1T7SkJWN2t8EZO5yVkyg2d/j fZfbonQsjS/2zSLwL/7OLr9sgBL2nRjsDzwLqQUfzz5DXFz+JDFBdfouUkbjJmgqtx6s 1LTDLoytBf2qy/DWfrkNop0vpOCiIGseLYImYVJbAlKxOmfsT38h9kc4uVxXuP1dyqV1 YnBTP7IFnl3sVgCOTlWOk41QL/RdWHA3hGF1BQaZCaKiYabS7T4IxGQqmiqEDwCwms/j 3jXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=JKd/c1e9MQ+nWPR0mewY90955nZJz0S21qiaRcGcGZk=; b=LINCFb50MoJP032TzfLBsvRP8cC8EEXeT7Ln0D0m08n6eKptugDmtn+cyJEi+OtUFC iH0o3KPe21e7Qlc7li8j73Nk9bcz783sDZNEIo3jRC6qf37VRvHv9HPIlbTRVkJuZqZu Q53N9lsYGuRWZUzzTBg7cQVvR6+YH4XZg0Ed/zYuGNPZEMsKtm9k1JPFc73kY3r1R9zo eaMmyi7kHT/ksbtrD1LJNF+9yCc9JlRq7pYSI0MmpT7hgt8kPjVGvPDy7aSwymd5SDRt +CS96dTK471CUYnaIAgU05H21gb+xB2BWzVIPFUzu89UhM5FuutSVeJjdC7Xzj0LJcxd Pw5Q== X-Gm-Message-State: AOAM530YPd3JOYCQBVwXFHu4GUQnm/jPPRWe5fqJVhgfsEBI96U6e6M+ duChhxSSI7xY4iqwqu35nWBuNaPUOQhcI6Uw5BaNqS1K X-Google-Smtp-Source: ABdhPJwAzAaXby4GvtCgJfcEG9i4KSpdOQE9KURov83BCFVVvTNQ+XAPwu4U2WssJOW5RApx9zzg/jebj+VfEr9itMM= X-Received: by 2002:aca:4257:: with SMTP id p84mr1971644oia.68.1608126149508; Wed, 16 Dec 2020 05:42:29 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Rajesh Kumar Date: Wed, 16 Dec 2020 19:12:13 +0530 Message-ID: Subject: Re: Netmap Library not getting installed on custom kernel installation To: freebsd-net@freebsd.org, FreeBSD Hackers X-Rspamd-Queue-Id: 4CwxBt6ZFLz4vT7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=ULWit7Kr; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rajfbsd@gmail.com designates 2607:f8b0:4864:20::22b as permitted sender) smtp.mailfrom=rajfbsd@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::22b:from]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[0.995]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::22b:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::22b:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-net,freebsd-hackers]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 13:42:31 -0000 Hi, Got around this issue by manually copying necessary in /usr/obj Looks like libnetmap (src/lib/libnetmap) is not built and installed by default. Manually built them and copied the "libnetmap.h" and "libnetmap.so" (not just the header file) to appropriate directories in /usr/obj helps to get past the issue. But not sure why libnetmap is not built and installed though "device netmap" is set in the config file. Manually copying may not be the right approach. Can anyone suggest a cleaner way of getting things done? Thanks, Rajesh. On Wed, Dec 16, 2020 at 3:33 PM Rajesh Kumar wrote: > Hi, > > I am trying to compile the netmap tools(pkt-gen, bridge etc.,) and getting > the below error. > > > > > > */root//freebsd/tools/tools/netmap/pkt-gen.c:47:10: fatal error: > 'libnetmap.h' file not found#include ^~~~~~~~~~~~~1 > error generated.*** Error code 1* > > On debug, I don't see the libnetmap.h file getting installed in the > /usr/obj/ directory. Whereas, in another similar machine I have the file > in /usr/obj and compilation of netmap tools goes fine. For the test, I > just copied libnetmap.h from the source and it leads to linker error. So > seems the libnetmap library is not installed properly. > > I installed a custom kernel just disabling the debug options with the > FreeBSD-CURRENT branch. After rebooting to the custom kernel, I tried to > compile the netmap tools (with some changes) and ran into the above error. > > How to get the netmap tools compiled in this scenario? Am i missing > something? > From owner-freebsd-hackers@freebsd.org Wed Dec 16 14:34:48 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C6A304BE1C4; Wed, 16 Dec 2020 14:34:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CwyMC5dxPz3F5s; Wed, 16 Dec 2020 14:34:47 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x335.google.com with SMTP id y23so2659946wmi.1; Wed, 16 Dec 2020 06:34:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=a6NwnUJgbH0vSUkBPRucxiUCTxUHotf1DA2yp2WiaVE=; b=EJ8iJZwJmPgeVyyaqFSUESVzhMXWZdsn7+Ez34J1cAmyBat3oBNvjIE7Hzhwkt5pIs GP9Mdysi2eRAJ+tu3GIf7igj/4Dlor4RnwLeNfiFeWd/cmMxgCGM8a9w9ZsvSt7t+8GB nAu3bFoewZyWJNWNFZUDCDCd2tFGM9NF1/n1/3b+p508Y7EF3HqA+g5LBrbhCWJD9kY2 qUinOen0UkzSR4smVRFl68gaIS0z5lbIYqDjd9bL/GF17YIntC5kGPq4C6vhgkpQvwL7 qrYb8s+0aOR8gqNYxDTVzeiuiBYVcIRfE8Y8ZTFO/malu99T2E+p3l/57Yc+tQWVD0/r vbNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=a6NwnUJgbH0vSUkBPRucxiUCTxUHotf1DA2yp2WiaVE=; b=j81VD/c2X916e1M8lUgxoq3sa4gcwIDkdv5yFUjpodVektuxeCn31z+1ylMhPlIhJR J+sZZDBdy8GNtAxfOVitZxWYKgXI5ltRlvpC7qxtQAzpmVyN1V4r8rlhEG6xKuNioei+ lSX8qcFSM963OwvC+GIHjpN/yDPpPhQuDmFZVvlfSXpcE21SCpgxclAeLiiTHlfgNYHl xgwPaXfg+X+NaVm+PTq5udQDqRkZkOXfRBH4uWB33VWt2I5+VQ0NdwhVZJX2LJ+oEuce F8QWfj4sslN/ZhGHfSYj5mYGhLWW3me0P0+i8/FiKGoHbKHP0f5i+IpneLcnbhRgDXBz aB8g== X-Gm-Message-State: AOAM532dAVOYtYrjtf+phf8o1NnZH5Hkp0blJ8sh+8XS9KrSgfpxpHrJ McHfBlq5nqQEcl20WetEVM0= X-Google-Smtp-Source: ABdhPJxSFAYzc9Rj+mFzQMAdR47MuOagt5CZBPuEMo35K4sguKi8j9IwL8u82auvFKyxcwr7BqfSXw== X-Received: by 2002:a1c:4c11:: with SMTP id z17mr3525154wmf.13.1608129285513; Wed, 16 Dec 2020 06:34:45 -0800 (PST) Received: from ernst.home (p5b02350e.dip0.t-ipconnect.de. [91.2.53.14]) by smtp.gmail.com with ESMTPSA id m81sm3220391wmf.29.2020.12.16.06.34.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Dec 2020 06:34:44 -0800 (PST) Date: Wed, 16 Dec 2020 15:34:43 +0100 From: Gary Jennejohn To: Rajesh Kumar Cc: freebsd-net@freebsd.org, FreeBSD Hackers Subject: Re: Netmap Library not getting installed on custom kernel installation Message-ID: <20201216143443.124709e8@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4CwyMC5dxPz3F5s X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=EJ8iJZwJ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::335 as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-2.03 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a00:1450:4864:20::335:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[91.2.53.14:received]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.97)[0.971]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; SPAMHAUS_ZRD(0.00)[2a00:1450:4864:20::335:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::335:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-net,freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 14:34:48 -0000 On Wed, 16 Dec 2020 19:12:13 +0530 Rajesh Kumar wrote: > Hi, > > Got around this issue by manually copying necessary in /usr/obj > > Looks like libnetmap (src/lib/libnetmap) is not built and installed by > default. Manually built them and copied the "libnetmap.h" and > "libnetmap.so" (not just the header file) to appropriate directories in > /usr/obj helps to get past the issue. But not sure why libnetmap is not > built and installed though "device netmap" is set in the config file. > > Manually copying may not be the right approach. Can anyone suggest a > cleaner way of getting things done? > libnetmap is built with buildworld, not buildkernel. It's a user-land library and has nothing to do with "device netmap" being set in the kernel configuration file. I did buildworld and installworld on Sunday (Dec 13th) and libnetmap was newly built and newly installed, as expected. > Thanks, > Rajesh. > > On Wed, Dec 16, 2020 at 3:33 PM Rajesh Kumar wrote: > > > Hi, > > > > I am trying to compile the netmap tools(pkt-gen, bridge etc.,) and getting > > the below error. > > > > > > > > > > > > */root//freebsd/tools/tools/netmap/pkt-gen.c:47:10: fatal error: > > 'libnetmap.h' file not found#include ^~~~~~~~~~~~~1 > > error generated.*** Error code 1* > > > > On debug, I don't see the libnetmap.h file getting installed in the > > /usr/obj/ directory. Whereas, in another similar machine I have the file > > in /usr/obj and compilation of netmap tools goes fine. For the test, I > > just copied libnetmap.h from the source and it leads to linker error. So > > seems the libnetmap library is not installed properly. > > > > I installed a custom kernel just disabling the debug options with the > > FreeBSD-CURRENT branch. After rebooting to the custom kernel, I tried to > > compile the netmap tools (with some changes) and ran into the above error. > > > > How to get the netmap tools compiled in this scenario? Am i missing > > something? > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Gary Jennejohn From owner-freebsd-hackers@freebsd.org Wed Dec 16 20:53:33 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5CF224C6D87; Wed, 16 Dec 2020 20:53:33 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cx6mF20fCz3tkF; Wed, 16 Dec 2020 20:53:33 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: vmaffione) by smtp.freebsd.org (Postfix) with ESMTPSA id 3508DC0A9; Wed, 16 Dec 2020 20:53:33 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: by mail-pf1-f170.google.com with SMTP id q22so17359429pfk.12; Wed, 16 Dec 2020 12:53:33 -0800 (PST) X-Gm-Message-State: AOAM533ihVU1TSSgsnX43iol+jz9vuEfkvRLGevSQhd0Bs/kYin+BuCx k0iICbCR/J1rK3K6GP5OSFIsFKulZdmHH77tk34= X-Google-Smtp-Source: ABdhPJzqAj+Yv/p4LuoOxLYOxkpirKrUTct+f5xE0K3BHc5EDusKg7wCQanpnIstV66l6qnlANDML5gKGnZ2YN3IGYg= X-Received: by 2002:a63:2264:: with SMTP id t36mr34348254pgm.350.1608152012251; Wed, 16 Dec 2020 12:53:32 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vincenzo Maffione Date: Wed, 16 Dec 2020 21:53:21 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Netmap Library not getting installed on custom kernel installation To: Rajesh Kumar Cc: "freebsd-net@freebsd.org" , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 20:53:33 -0000 Hi Rajesh, The libnetmap library is part of the userland utilities, whereas netmap itself is a kernel subsystem. This means that when you enable "device netmap", and you run "make buildkernel", you get a kernel with netmap included. Also the low level kernel headers are installed (e.g. /usr/include/net/netmap.h). On the other hand, libnetmap gets installed (libnetmap.h + libnetmap.so + libnetmap.a + ...) when you run "make buildworld" and "make installworld", because that's a userland component. On a side note, the netmap tools (pkt-gen, bridge, lb, etc.) should really be a port. Another TODO item. Regards, Vincenzo Il giorno mer 16 dic 2020 alle ore 14:42 Rajesh Kumar ha scritto: > Hi, > > Got around this issue by manually copying necessary in /usr/obj > > Looks like libnetmap (src/lib/libnetmap) is not built and installed by > default. Manually built them and copied the "libnetmap.h" and > "libnetmap.so" (not just the header file) to appropriate directories in > /usr/obj helps to get past the issue. But not sure why libnetmap is not > built and installed though "device netmap" is set in the config file. > > Manually copying may not be the right approach. Can anyone suggest a > cleaner way of getting things done? > > Thanks, > Rajesh. > > On Wed, Dec 16, 2020 at 3:33 PM Rajesh Kumar wrote: > > > Hi, > > > > I am trying to compile the netmap tools(pkt-gen, bridge etc.,) and > getting > > the below error. > > > > > > > > > > > > */root//freebsd/tools/tools/netmap/pkt-gen.c:47:10: fatal error: > > 'libnetmap.h' file not found#include ^~~~~~~~~~~~~1 > > error generated.*** Error code 1* > > > > On debug, I don't see the libnetmap.h file getting installed in the > > /usr/obj/ directory. Whereas, in another similar machine I have the file > > in /usr/obj and compilation of netmap tools goes fine. For the test, I > > just copied libnetmap.h from the source and it leads to linker error. So > > seems the libnetmap library is not installed properly. > > > > I installed a custom kernel just disabling the debug options with the > > FreeBSD-CURRENT branch. After rebooting to the custom kernel, I tried to > > compile the netmap tools (with some changes) and ran into the above > error. > > > > How to get the netmap tools compiled in this scenario? Am i missing > > something? > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Thu Dec 17 13:19:04 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 45BF44B7A98 for ; Thu, 17 Dec 2020 13:19:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CxXdN1QMtz3Pjr for ; Thu, 17 Dec 2020 13:19:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 30A7F4B7566; Thu, 17 Dec 2020 13:19:04 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 307154B7A97 for ; Thu, 17 Dec 2020 13:19:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CxXdN0s5dz3PgP; Thu, 17 Dec 2020 13:19:04 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: lev/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id E8C9C233E3; Thu, 17 Dec 2020 13:19:03 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.168.23.230] (unknown [89.113.128.32]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id 7B66F5674; Thu, 17 Dec 2020 16:19:00 +0300 (MSK) Reply-To: lev@FreeBSD.org Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? To: Warner Losh , Poul-Henning Kamp Cc: "freebsd-hackers@freebsd.org" References: <25469.1608040822@critter.freebsd.dk> <26111.1608051101@critter.freebsd.dk> From: Lev Serebryakov Organization: FreeBSD Message-ID: <63257157-9cdd-0da4-f061-4005319514c2@FreeBSD.org> Date: Thu, 17 Dec 2020 16:18:59 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 13:19:04 -0000 On 15.12.2020 23:10, Warner Losh wrote: > On Tue, Dec 15, 2020 at 9:51 AM Poul-Henning Kamp >>> It is intentional. UEFI really doesn't want you using non-standard >>> partition flags to determine boot order. >> >> So how would one go about doing "boot0/nanobsd-style" dual >> root the "proper" way in an UEFI environment ? >> > > By using gptboot.efi in the ESP and placaing loader.efi in the UFS > partitions... But You've said, that: > UEFI has its own bootnext protocol, that works in conjunction with the EFI > environment variables to have a more robust, less 'guess what I mean' > approach. So all in all, it's hard, non-standard and doesn't play well with > UEFI." Could it be used here? -- // Lev Serebryakov From owner-freebsd-hackers@freebsd.org Thu Dec 17 14:18:43 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 507504B909B; Thu, 17 Dec 2020 14:18:43 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CxYyC1mlNz3k51; Thu, 17 Dec 2020 14:18:43 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: olivier/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 2D1E123A39; Thu, 17 Dec 2020 14:18:43 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: by mail-lf1-f43.google.com with SMTP id h205so14218574lfd.5; Thu, 17 Dec 2020 06:18:43 -0800 (PST) X-Gm-Message-State: AOAM5314Pygm3WQ3WyzDFRebaKzjLf5+vRCSxpbR+4RzvroDm27ESqq5 fmS8DWQfBeKLTAd8vol2dAHAJnYVv5mTU6ENgr0= X-Google-Smtp-Source: ABdhPJx1iUt+Cdu64uNf8yGp7bGmmISnmb1HfeW3gNt4P5GKbCsfjNL8yaVKjKMA836nC+K0eQfhZ5KJfFGO3WdwoCk= X-Received: by 2002:a2e:9916:: with SMTP id v22mr8276605lji.221.1608214721678; Thu, 17 Dec 2020 06:18:41 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Thu, 17 Dec 2020 15:18:30 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Netmap Library not getting installed on custom kernel installation To: Vincenzo Maffione Cc: Rajesh Kumar , "freebsd-net@freebsd.org" , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 14:18:43 -0000 On Wed, Dec 16, 2020 at 9:53 PM Vincenzo Maffione wrote: > > On a side note, the netmap tools (pkt-gen, bridge, lb, etc.) should really > be a port. Another TODO item. > > There is already one port for an old version of pkt-gen: https://svnweb.freebsd.org/ports/head/net/pkt-gen/ And here is a custom port's patch to upgrade this port to a not-so-old version including a quick&dirty range bug fix (cleaner version fresh-from-today official netmap github), and adding a new option to prevent doing software IP & UDP checksum by default (because it consumes a lot of ressource on 40G or 100G NIC and Chelsio NIC are able to do hardware checksum in netmap mode): https://github.com/ocochard/BSDRP/blob/master/BSDRP/patches/ports.pkt-gen.patch Regards, Olivier From owner-freebsd-hackers@freebsd.org Thu Dec 17 17:41:58 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 61DE74BDA7A for ; Thu, 17 Dec 2020 17:41:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CxfSk0byrz4SwH for ; Thu, 17 Dec 2020 17:41:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.nyi.freebsd.org (Postfix) id 14B0F4BE09C; Thu, 17 Dec 2020 17:41:58 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 147904BE015 for ; Thu, 17 Dec 2020 17:41:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CxfSj6y4Dz4StK for ; Thu, 17 Dec 2020 17:41:57 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf32.google.com with SMTP id l7so13683311qvt.4 for ; Thu, 17 Dec 2020 09:41:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Qohrv6NQQggoqoWa0FeF27PBGacjmcleq6mvSi59IRc=; b=jL5QIIO3j7ZdEcIdFyTj4ywho8XePZpQ0A1Y0STNZBdIS6cuv/kCdgbcqb5vbDNLwP g/LtaNXnffIZo5LvwYjb+zv2WLak+MdRD9o1bbIgJ8A7vnrKXkmCHISDoIXKmLfqN5oU KU87aeQHcoalUpcYwmoQ8y++XKt6mgw64sO6cmlPTS5ogewHM7bIAYVzH9q3zIVeFvSn nXQ4L2xgJ63Pdhz+YXCeb+WV573xx7ULVwSjQdWLCFieOhIh1UJry1H6hRuGJbTzM65R KvgC2HmquUN1zzezOe3t3+SMD90iwrpZ/2L1GK/Awid3cL2QUiIbNDRdp80pY6roUxIu XXBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Qohrv6NQQggoqoWa0FeF27PBGacjmcleq6mvSi59IRc=; b=daubV3PL5cbZXebEFdF5jWZU1sdApE4+XQIsf+jVEK6P+ssfjYXK4Vu5rXbgDjUM3O 7sXigOVvi1NEnh2eqPKgYvra5yDNAbKJvrfpvDn4MSfFV2xWMjQDBLAx9OD4vO903HiF S0kVZ5DEwmK2A+XH7Fs8Gj8yTZNuiOZo8rfRuYottqK+rTKUnTx5aWnt6G7AzbeWJs/E xXpKI9Rr0I7+1umAzbAcBgCnt0VL2AVBXqAi31aC+fQYLEy2QOMn1q139WkhpZ4zmq0s zwAGZ6Jk9I17ptm6doDW4PwM77+PBfpbyABuD5XtvkxK5CifmhK84rV6FPviZpUmb9Zt q/bg== X-Gm-Message-State: AOAM5330t8524euRuZMewwUSkueGK8UC+/55HLwWY6UHpVI5flpxkf++ baC1dSk17aSF523Kc7L+0eUo/b/Wdyh3Z4jI9f2iGS4qpQCMoQ== X-Google-Smtp-Source: ABdhPJynuTroxhW4M8M7Hde0+TMUIZJsEdW9KnZUQ9nkhpY0zi2JiK2zTG+E54naEcXcPz2ohs0F67FsFLuDhHkVEG8= X-Received: by 2002:ad4:5b82:: with SMTP id 2mr161578qvp.28.1608226916681; Thu, 17 Dec 2020 09:41:56 -0800 (PST) MIME-Version: 1.0 References: <25469.1608040822@critter.freebsd.dk> <26111.1608051101@critter.freebsd.dk> <63257157-9cdd-0da4-f061-4005319514c2@FreeBSD.org> In-Reply-To: <63257157-9cdd-0da4-f061-4005319514c2@FreeBSD.org> From: Warner Losh Date: Thu, 17 Dec 2020 10:41:46 -0700 Message-ID: Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? To: Lev Serebryakov Cc: Poul-Henning Kamp , "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: 4CxfSj6y4Dz4StK X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 17:41:58 -0000 On Thu, Dec 17, 2020 at 6:19 AM Lev Serebryakov wrote: > On 15.12.2020 23:10, Warner Losh wrote: > > On Tue, Dec 15, 2020 at 9:51 AM Poul-Henning Kamp > > >>> It is intentional. UEFI really doesn't want you using non-standard > >>> partition flags to determine boot order. > >> > >> So how would one go about doing "boot0/nanobsd-style" dual > >> root the "proper" way in an UEFI environment ? > >> > > > > By using gptboot.efi in the ESP and placaing loader.efi in the UFS > > partitions... > But You've said, that: > > > UEFI has its own bootnext protocol, that works in conjunction with the > EFI > > environment variables to have a more robust, less 'guess what I mean' > > approach. So all in all, it's hard, non-standard and doesn't play well > with > > UEFI." > > Could it be used here? > Yes. It can. Warner From owner-freebsd-hackers@freebsd.org Thu Dec 17 18:52:19 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0E2604C01E8 for ; Thu, 17 Dec 2020 18:52:19 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4Cxh1t5vPsz4Zyh for ; Thu, 17 Dec 2020 18:52:18 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.nyi.freebsd.org (Postfix) id AA6654C02C0; Thu, 17 Dec 2020 18:52:18 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A646F4C01E7 for ; Thu, 17 Dec 2020 18:52:18 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cxh1s51ytz4Zjj; Thu, 17 Dec 2020 18:52:16 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id EE8B38A3C8; Thu, 17 Dec 2020 18:52:07 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.16.1/8.16.1) with ESMTPS id 0BHIq6Hi062926 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 17 Dec 2020 18:52:06 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.16.1/8.16.1/Submit) id 0BHIq6Uu062923; Thu, 17 Dec 2020 18:52:06 GMT (envelope-from phk) To: Warner Losh cc: Lev Serebryakov , "freebsd-hackers@freebsd.org" Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? In-reply-to: From: "Poul-Henning Kamp" References: <25469.1608040822@critter.freebsd.dk> <26111.1608051101@critter.freebsd.dk> <63257157-9cdd-0da4-f061-4005319514c2@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <62921.1608231126.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Thu, 17 Dec 2020 18:52:06 +0000 Message-ID: <62922.1608231126@critter.freebsd.dk> X-Rspamd-Queue-Id: 4Cxh1s51ytz4Zjj X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 18:52:19 -0000 -------- Warner Losh writes: > > > UEFI has its own bootnext protocol, that works in conjunction with = the EFI > > > environment variables to have a more robust, less 'guess what I mea= n' > > > approach. So all in all, it's hard, non-standard and doesn't play w= ell with > > > UEFI." > > > > Could it be used here? > > > > Yes. It can. Do you know of any good sources of documentation ? -- = 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-hackers@freebsd.org Thu Dec 17 19:02:24 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BB75E4C0C7A for ; Thu, 17 Dec 2020 19:02:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4CxhFX3G0Yz4bng for ; Thu, 17 Dec 2020 19:02:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.nyi.freebsd.org (Postfix) id 6FCA74C09BA; Thu, 17 Dec 2020 19:02:24 +0000 (UTC) Delivered-To: hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F9034C0BF6 for ; Thu, 17 Dec 2020 19:02:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CxhFX2PW9z4byc for ; Thu, 17 Dec 2020 19:02:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x829.google.com with SMTP id z3so20842516qtw.9 for ; Thu, 17 Dec 2020 11:02:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Cuo48uKRPSaRg2xv81q4ZnMFxv2mIFrUyT1vY1p/5FU=; b=roLDx41YiA4QsGJl5YOroxFamh30gdiSq9BUMAcllF8IheVCi/Bw3m1S+6G0PxQwIr 2y4iT0DL7cl0ZEhRHVlUbd2gow/jx4ajEPsfaWr/dfMAejZOfab+dmvTiut8fmZaixzE YPQdvc+kdLVcyzYxNd7Jypdx0na6gTQzkJkh734Y5tQiIIkwFgMZlW5YP4tl+Avn8Ugi YkQGFzgG+CdbPXLwFCpHc/g9b91DD+HYFA5O4Cb6WGyWN13IYInSKupRWpGS5ANf5V6E 8mIm8BAv0S4vKe3Yq1tpBPLAMTg8e4zcIXfwbn5oU25inXU7hmUkNm+SWw8O9CR8V0pz 1rCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cuo48uKRPSaRg2xv81q4ZnMFxv2mIFrUyT1vY1p/5FU=; b=TmGjQDTrYxdROWS4dnoP9TapHijsj0BtRqU5ld2Jc+49vxDP+YuLUaKcZz6jrL0464 uRYeZ0obyw8VZJOociI3L9R3GapdiYhvWcOxPKng2mZcJIn1YbpM4b1zZa+hNmuxwidY JFGta5YaMM1ZRLs7L3RkZpULslF9JjqXpilshXGz0+sYUjYqROvLahWzbnd048MYPSeO 4k7ouU65CrI8OvIOZEKTcJ3RtxJt+9jrSIi6x7p82dFDFgZ876VNaGnp1BIUL0Lv9hNp V1pMXhJQb6iGJ/ouRHfpWT6dMIo8RF8HOGIOSQhl/vA8MGFs2e848l7fLj0YYkvY+Y3U jKqQ== X-Gm-Message-State: AOAM5317srvrCDvEmqW1tn3xtV66NxDm1OIsWglQOMz0dGK1Xr2aecJK yQPJ79Qye0pSxhKycI/6MXZdHcSZ5C7Gj5bmX+kBP4XPTi15YQ== X-Google-Smtp-Source: ABdhPJxssCi2VMLRV7npAWnlRMqBMsqIbxWrYpkjq28usII08cl6H/fu9DOi1ovYkaKkRezsnUULrga/EGd0N0qsvxY= X-Received: by 2002:ac8:58d2:: with SMTP id u18mr160473qta.235.1608231743255; Thu, 17 Dec 2020 11:02:23 -0800 (PST) MIME-Version: 1.0 References: <25469.1608040822@critter.freebsd.dk> <26111.1608051101@critter.freebsd.dk> <63257157-9cdd-0da4-f061-4005319514c2@FreeBSD.org> <62922.1608231126@critter.freebsd.dk> In-Reply-To: <62922.1608231126@critter.freebsd.dk> From: Warner Losh Date: Thu, 17 Dec 2020 12:02:12 -0700 Message-ID: Subject: Re: Should/does loader.efi respect the "bootme" GPT attribute ? To: Poul-Henning Kamp Cc: Lev Serebryakov , "freebsd-hackers@freebsd.org" X-Rspamd-Queue-Id: 4CxhFX2PW9z4byc X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 19:02:24 -0000 On Thu, Dec 17, 2020 at 11:52 AM Poul-Henning Kamp wrote: > -------- > Warner Losh writes: > > > > > UEFI has its own bootnext protocol, that works in conjunction with > the EFI > > > > environment variables to have a more robust, less 'guess what I > mean' > > > > approach. So all in all, it's hard, non-standard and doesn't play > well with > > > > UEFI." > > > > > > Could it be used here? > > > > > > > Yes. It can. > > Do you know of any good sources of documentation ? > Chapter 3 of the UEFI spec has the canonical reference for the Boot Manager specification. If your mobo understands setting persistent UEFI variables, that's the most robust way to do things. There's not a FreeBSD document, though efibootmgr comes closest and would be what you'd use to manage... Warner From owner-freebsd-hackers@freebsd.org Thu Dec 17 22:42:46 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 93F114C69AA; Thu, 17 Dec 2020 22:42:46 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cxn7p3gVKz4tST; Thu, 17 Dec 2020 22:42:46 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: vmaffione) by smtp.freebsd.org (Postfix) with ESMTPSA id 68EBB282C8; Thu, 17 Dec 2020 22:42:46 +0000 (UTC) (envelope-from vmaffione@freebsd.org) Received: by mail-pj1-f42.google.com with SMTP id iq13so220706pjb.3; Thu, 17 Dec 2020 14:42:46 -0800 (PST) X-Gm-Message-State: AOAM5306uKNK9ma6ZIGD88JTugZZKWDe3mp//IwE/eMibJEJOCR+cwM8 5NS28G1qEYxFUher/sB+rCKuekI7etgfmx7w00I= X-Google-Smtp-Source: ABdhPJyw4tJJRkcM1RUgZ6h8skTnN93nl+BD3x4DP8Qxv8Ki9TIBXoRgJET3LWB/fS/p+WrCqT7XlGUBW2RAB2xvM9o= X-Received: by 2002:a17:90a:4dcd:: with SMTP id r13mr1353911pjl.74.1608244965212; Thu, 17 Dec 2020 14:42:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vincenzo Maffione Date: Thu, 17 Dec 2020 23:42:33 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Netmap Library not getting installed on custom kernel installation To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: Rajesh Kumar , "freebsd-net@freebsd.org" , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 22:42:46 -0000 Il giorno gio 17 dic 2020 alle ore 15:18 Olivier Cochard-Labb=C3=A9 < olivier@freebsd.org> ha scritto: > On Wed, Dec 16, 2020 at 9:53 PM Vincenzo Maffione > wrote: > >> >> On a side note, the netmap tools (pkt-gen, bridge, lb, etc.) should real= ly >> be a port. Another TODO item. >> >> > There is already one port for an old version of pkt-gen: > https://svnweb.freebsd.org/ports/head/net/pkt-gen/ > > Thanks. I would however prefer to have a "netmap-tools" port, so that you get all the basic applications at once. They are actually just 4-5, so it is worth avoiding multiple ports. And here is a custom port's patch to upgrade this port to a not-so-old > version including a quick&dirty range bug fix (cleaner version > fresh-from-today official netmap github), and adding a new option to > prevent doing software IP & UDP checksum by default (because it consumes = a > lot of ressource on 40G or 100G NIC and Chelsio NIC are able to do hardwa= re > checksum in netmap mode): > > https://github.com/ocochard/BSDRP/blob/master/BSDRP/patches/ports.pkt-gen= .patch > > I see. That should be pushed on the github (and then reflected on the src tree). The current netmap tools that live in tools/tools/netmap are actually aligned with the github. Thanks, Vincenzo > Regards, > > Olivier > > > From owner-freebsd-hackers@freebsd.org Sat Dec 19 12:02:49 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DDCD34C55FE for ; Sat, 19 Dec 2020 12:02:49 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from smtp.smtpout.orange.fr (smtp08.smtpout.orange.fr [80.12.242.130]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CykrS6FJ9z3MvN for ; Sat, 19 Dec 2020 12:02:48 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from [192.168.1.17] ([90.112.25.211]) by mwinf5d67 with ME id 6C2k240044ZGaNJ03C2kRy; Sat, 19 Dec 2020 13:02:45 +0100 X-ME-Helo: [192.168.1.17] X-ME-Auth: cGpmbG95ZEB3YW5hZG9vLmZy X-ME-Date: Sat, 19 Dec 2020 13:02:45 +0100 X-ME-IP: 90.112.25.211 To: FreeBSD Hackers From: Paul Floyd Subject: pthread_self() problem in DRD Message-ID: <61236c3a-05b8-7986-e95d-a9369eaf522b@wanadoo.fr> Date: Sat, 19 Dec 2020 13:02:46 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 Content-Language: en-GB X-Rspamd-Queue-Id: 4CykrS6FJ9z3MvN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pjfloyd@wanadoo.fr has no SPF policy when checking 80.12.242.130) smtp.mailfrom=pjfloyd@wanadoo.fr X-Spamd-Result: default: False [-2.10 / 15.00]; FREEMAIL_FROM(0.00)[wanadoo.fr]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[wanadoo.fr]; ASN(0.00)[asn:3215, ipnet:80.12.240.0/20, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[80.12.242.130:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[wanadoo.fr]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[80.12.242.130:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[80.12.242.130:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[80.12.242.130:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-hackers] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2020 12:02:49 -0000 Hi I'm trying to debug an issue in DRD (a thread hazard detection tool, part of Valgrind). There is an issue when using shared libraries. A detailed description is here https://github.com/paulfloyd/freebsd_valgrind/issues/57 In short, the flow of events is 1. [guest] The DRD init function gets called (as it is marked __attribute__((constructor)) 2. [guest] DRD init sets the current thread id, calling pthread_self() and using a client request. 3. [host] DRD_(thread_set_pthreadid)() gets called, and it is passed the DRD tid and the value obtained from pthread_self(). 4. [guest] The testcase does a dlopen() and then calls a function in the shared library 5. [guest] the shard lib function calls pthread_create 6. [host] pthread_create gets intercepted and performs another call to DRD_(set_pthread_id)() I've marked thinks as guest/host, in reality there is only one process executing. The problem is that the thread id obtained in step 3 is not the same as the one obtained in step 6. The result is an assert. Two questions 1. Is there any reason why pthread_self() should return different values when executed from a constructor and then from a dlopen()'d function? 2. Is there any initialization code that affects the value returned by pthread_self()? It's possible that something is missing. A+ Paul From owner-freebsd-hackers@freebsd.org Sat Dec 19 12:20:59 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C28F84C5EAE for ; Sat, 19 Dec 2020 12:20:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CylFQ5nsxz3NLN for ; Sat, 19 Dec 2020 12:20:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.16.1/8.16.1) with ESMTPS id 0BJCKiM3045378 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 19 Dec 2020 14:20:47 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 0BJCKiM3045378 Received: (from kostik@localhost) by tom.home (8.16.1/8.16.1/Submit) id 0BJCKhHP045377; Sat, 19 Dec 2020 14:20:43 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 19 Dec 2020 14:20:43 +0200 From: Konstantin Belousov To: Paul Floyd Cc: FreeBSD Hackers Subject: Re: pthread_self() problem in DRD Message-ID: References: <61236c3a-05b8-7986-e95d-a9369eaf522b@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61236c3a-05b8-7986-e95d-a9369eaf522b@wanadoo.fr> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on tom.home X-Rspamd-Queue-Id: 4CylFQ5nsxz3NLN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:470:d5e7:1::1:from]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; SPAMHAUS_ZRD(0.00)[2001:470:d5e7:1::1:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_TO(0.00)[wanadoo.fr]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; MIME_TRACE(0.00)[0:+]; MAILMAN_DEST(0.00)[freebsd-hackers]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2020 12:20:59 -0000 On Sat, Dec 19, 2020 at 01:02:46PM +0100, Paul Floyd wrote: > Hi > > I'm trying to debug an issue in DRD (a thread hazard detection tool, part of > Valgrind). There is an issue when using shared libraries. > > A detailed description is here > > https://github.com/paulfloyd/freebsd_valgrind/issues/57 > > In short, the flow of events is > > 1. [guest] The DRD init function gets called (as it is marked > __attribute__((constructor)) > 2. [guest] DRD init sets the current thread id, calling pthread_self() > and using a client request. > 3. [host] DRD_(thread_set_pthreadid)() gets called, and it is passed > the DRD tid and the value obtained from pthread_self(). > 4. [guest] The testcase does a dlopen() and then calls a function in > the shared library > 5. [guest] the shard lib function calls pthread_create > 6. [host] pthread_create gets intercepted and performs another call to > DRD_(set_pthread_id)() > > > I've marked thinks as guest/host, in reality there is only one process > executing. > > > The problem is that the thread id obtained in step 3 is not the same as the > one obtained in step 6. The result is an assert. > > > Two questions > > 1. Is there any reason why pthread_self() should return different > values when executed from a constructor and then from a dlopen()'d > function? > 2. Is there any initialization code that affects the value returned by > pthread_self()? It's possible that something is missing. > It is impossible to say anything definitive without minimal self-contained example, but it is possible to make some guess. In FreeBSD, libc exports pthread stubs which main purpose is to satisfy linkage requirements of the shared objects that can work in multithreaded environment but do not require it. For instance, pthread_self() is exported from libc, and it returns a pointer to some internal non-sensical memory when called, until libthr is loaded and initialized. At the moment libthr is initialized, pthread_self() starts returning 'real' pthread_t. In your case, my guess is that one of two things happen: 1. you have first pthread_self() call from the process that does not have libthr loaded, then later dlopen(3) loads dso which is linked with libhtr. Second call to pthread_self() returns real pthread_t for main thread. 2. (less likely but possible to arrange) You process has libthr linked in, but your first call to pthread_self() from constructor occurs before constructors for libthr are run. Visible outcome is same. From owner-freebsd-hackers@freebsd.org Sat Dec 19 13:51:40 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4EA654C842D for ; Sat, 19 Dec 2020 13:51:40 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr [80.12.242.126]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CynG32rjrz3kyY for ; Sat, 19 Dec 2020 13:51:38 +0000 (UTC) (envelope-from pjfloyd@wanadoo.fr) Received: from [192.168.1.17] ([90.112.25.211]) by mwinf5d27 with ME id 6Dra240084ZGaNJ03DraHD; Sat, 19 Dec 2020 14:51:34 +0100 X-ME-Helo: [192.168.1.17] X-ME-Auth: cGpmbG95ZEB3YW5hZG9vLmZy X-ME-Date: Sat, 19 Dec 2020 14:51:34 +0100 X-ME-IP: 90.112.25.211 Subject: Re: pthread_self() problem in DRD To: freebsd-hackers@freebsd.org References: <61236c3a-05b8-7986-e95d-a9369eaf522b@wanadoo.fr> From: Paul Floyd Message-ID: Date: Sat, 19 Dec 2020 14:51:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-Rspamd-Queue-Id: 4CynG32rjrz3kyY X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pjfloyd@wanadoo.fr has no SPF policy when checking 80.12.242.126) smtp.mailfrom=pjfloyd@wanadoo.fr X-Spamd-Result: default: False [-0.10 / 15.00]; FREEMAIL_FROM(0.00)[wanadoo.fr]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[wanadoo.fr]; ASN(0.00)[asn:3215, ipnet:80.12.240.0/20, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[80.12.242.126:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[wanadoo.fr]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[80.12.242.126:from:127.0.2.255]; NEURAL_SPAM_SHORT(1.00)[1.000]; RCVD_IN_DNSWL_NONE(0.00)[80.12.242.126:from]; R_SPF_NA(0.00)[no SPF record]; RWL_MAILSPIKE_POSSIBLE(0.00)[80.12.242.126:from]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-hackers] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2020 13:51:40 -0000 > It is impossible to say anything definitive without minimal self-contained > example, but it is possible to make some guess. Here is the source /* dlopen_main.c */ #include #include #include #include "dlopen_lib.h" int main(int argc, char **argv) {   const char *lib = argc > 1 ? argv[1] : "./libfoo.so";   void *handle;   void (*function)();   const char *error;   handle = dlopen(lib, RTLD_NOW);   if (!handle) {     fputs (dlerror(), stderr);     exit(1);   }   function = dlsym(handle, "foo");   error = dlerror();   if (error)  {     fputs(error, stderr);     exit(1);   }   (*function)();   dlclose(handle);   return 0; } /* dlopen_lib.c */ #include #include #include #include "dlopen_lib.h" void *PrintHello(void *threadid) {   const long tid = (uintptr_t)threadid;   printf("Hello World! It's me, thread #%ld!\n", tid);   pthread_exit(NULL); } void foo() {   pthread_t thread;   int rc;   uintptr_t t = 1;   printf("In main: creating thread %ld\n", t);   rc = pthread_create(&thread, NULL, PrintHello, (void *)t);   if (rc)     printf("ERROR; return code from pthread_create() is %d\n", rc);   else     pthread_join(thread, NULL); } Command to execute: valgrind -tool=drd -q ./dlopen_main ./dlopen_lib.so > In FreeBSD, libc exports pthread stubs which main purpose is to satisfy > linkage requirements of the shared objects that can work in multithreaded > environment but do not require it. For instance, pthread_self() is exported > from libc, and it returns a pointer to some internal non-sensical memory > when called, until libthr is loaded and initialized. At the moment libthr > is initialized, pthread_self() starts returning 'real' pthread_t. > > In your case, my guess is that one of two things happen: > 1. you have first pthread_self() call from the process that does not have > libthr loaded, then later dlopen(3) loads dso which is linked with libhtr. > Second call to pthread_self() returns real pthread_t for main thread. > 2. (less likely but possible to arrange) You process has libthr linked in, > but your first call to pthread_self() from constructor occurs before > constructors for libthr are run. Visible outcome is same. That sounds quite plausible. The valgrind tools do not link with any libraries themselves. I'll see what effect doing a dlopen of libthr.so in the DRD init function has. A+ Paul