From nobody Mon Nov 20 09:16:15 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYhhN4BkGz50xlb for ; Mon, 20 Nov 2023 09:16:20 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYhhM6Z0Xz3Cn9 for ; Mon, 20 Nov 2023 09:16:19 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=WzipBkEP; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::32a as permitted sender) smtp.mailfrom=paulf2718@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-407c3adef8eso16657585e9.2 for ; Mon, 20 Nov 2023 01:16:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700471778; x=1701076578; darn=freebsd.org; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=4x7aTwZDZsPMsg7/AWZACoOw3Q9+JuGRuEKUiDVepRw=; b=WzipBkEPb7P4Mc+OruQGt28FAkICN3nmAl1xfF8bvZ4shoP4RBLsAIV3q0iHjPexb6 Z+QOiUb0BcUUPkX2XZoPB3k5ofbn5BIKwm3pmv0U0IpPXXS/ttAl8mjr3H4m5mfiHDMI G94Fhkhc6sjM/7P/RRhKeNBojBHgvAOvERPUHX/hZC9OPXtuUolIu1EKaHJPsnFK6AII EwmwhU79xGarOF2IE4TdmIcvDydCDAHNcV2XiX2UTx5RBZUx4bSzSqhFD1l3ZdlrOr0p 1h/I/mUX0aBQyxYeh9B2xfqsSZrxVsJtqPO2TpwDFvcgGHM61L4KP1QwvoN02Et65/7U Y6Qg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700471778; x=1701076578; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=4x7aTwZDZsPMsg7/AWZACoOw3Q9+JuGRuEKUiDVepRw=; b=noTmiiKWdwBxpyzqyWP4GXZ0BL4BuwgEgekc0hTbk9gYFEb5b1aTAYe2wH93fi8Gzp pphZ24mHRhBOEKfLANDbEkhPJbJ0KZyD8xEkfVprXPgBvE9tw66m7KI7I3EjzM6PZuma kF8q1NWAJE2hiimKBohrgozUH8bAXUbZArHjF2zHWpO22Z78SEAFfh41HuaMlENFCzNI 4rBDPli7rHzQ0HR5bPtPGKAa/fgMR7oatSyIEUWr/voQc1PrSu0N/UtavFH/SAQI8TU5 lTRkweqr70QOjuLub2YE+0UjTkk0qPeoln4Lk8DKXoU/lBW8TjzjsOaLwbX4IbnhBW6J vu+w== X-Gm-Message-State: AOJu0YyMYzOSVxnEBMEZq8SMYqrzzRIpk7VBfejWWjuCdOZaGf340H3E cK1phgf03p1Qvo8qJFb5ohh7IRPxcm8= X-Google-Smtp-Source: AGHT+IE0WfQDefsMhsz+NZ8RmP9Z/1ikQ0LAgJLwKw9bDEJOslr5TkrkDBAPMYW3wWkyw3lu4viftg== X-Received: by 2002:a05:600c:35cb:b0:401:23fc:1f92 with SMTP id r11-20020a05600c35cb00b0040123fc1f92mr5664574wmq.25.1700471778151; Mon, 20 Nov 2023 01:16:18 -0800 (PST) Received: from [137.202.253.23] (nat-ies.mentorg.com. [192.94.31.2]) by smtp.gmail.com with ESMTPSA id r5-20020a05600c458500b003fefaf299b6sm12829222wmo.38.2023.11.20.01.16.17 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Nov 2023 01:16:17 -0800 (PST) Message-ID: Date: Mon, 20 Nov 2023 10:16:15 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: "freebsd-hackers@FreeBSD.org" From: Paul Floyd Subject: FOSDEM 24 devroom Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32a:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SYhhM6Z0Xz3Cn9 X-Spamd-Bar: --- Hi There's a BSD devroom announced here https://www.freebsd.org/events/#fosdem-2024 but the link gives "Resource not found" and https://fosdem.org/2024/news/2023-11-08-devrooms-announced/ doesn't list BSD. Anyone know what is happening? A+ Paul From nobody Mon Nov 20 13:46:27 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYphB5bQQz51KVg for ; Mon, 20 Nov 2023 13:46:34 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 4SYph945YVz4Fcm for ; Mon, 20 Nov 2023 13:46:33 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=OpGLERPa; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=xzE3gvOa; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id A42CA3200A2F for ; Mon, 20 Nov 2023 08:46:31 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 20 Nov 2023 08:46:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm1; t=1700487991; x=1700574391; bh=8dfIgMahxP4dGElVQ48QreD1Y 7EBBnedkcpdNZsQ0XU=; b=OpGLERPaw1c4acP7qp5L55ZMlADuRfnDSSg9lAYJr Qt0sLCZyXTzzJTLBi7EBMkKzMGz1JC8QofzTJ6pNb3QB8Jnf64hfXniEVYEVSIUg 0YchYSqXp9nYU8GGFYlpwLfCPVRtzh8I3tW4nGBLMrCqXziSN343bSZv4oUO/Pu4 XG0+wt5MzrSUptZeX2pgRdgs00sPZfn+lrs/kVbwLqr2pIyr7Lqq9x0QfOaiF8Gq ZSrfcmg2tjFluxeAahZPkH5m5ac0EkSSw4xlz89T6BvbtUXlFe1bkL3nMWwMSpq4 9yx6KEytD7RztDuK4mocqgrFse1z1JElmWY5u0pN+YO+w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1700487991; x=1700574391; bh=8dfIgMahxP4dGElVQ48QreD1Y7EBBnedkcp dNZsQ0XU=; b=xzE3gvOagEaTKQtakMy6mJF4Sux8cL9x9WUqH20bhP4BMtQ/8Ne 9RnZawKy45chnyUv09mOkpM9PZIz8LgRSsL/8i1CgfUiQRs47/rQhkaTyW7XZLhs DiyhyNr0mawyfas/3jru3ugVhm0giiOZ7a8xUGQFSMKLjAuUq9DKuzKvWVq78v0P QcxrKWPEJvXNRmzyG0iSbR3L5l3eBfItiZKyQ/FzrRlBzYAgZV9cHlFGQdE6MzSo 97uc0gL2qv04k1bc3k3y2dKXsziCylTYQZFjCyo/uRGt1/9PaAOX5BdIVoVK4wlv 4JYejF+qlLyIR1b2fJGQaXsXrWBS8GHfZOA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudegjedgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtugesthdtredttd dtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgrthht vghrnhepueeuieffffejlefffeetudelheevveehkeeuvefgfeffgeefleekgeekkeekve evnecuffhomhgrihhnpehklhgrrhgrshihshhtvghmshdrtghomhenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 20 Nov 2023 08:46:30 -0500 (EST) Date: Mon, 20 Nov 2023 13:46:27 +0000 From: void To: freebsd-hackers@freebsd.org Subject: the RATELIMIT kernel option Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-5.00 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.24:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SYph945YVz4Fcm X-Spamd-Bar: ---- Hello hackers@, I've been looking at adding the RACK tcp kernel option, and reading the instructions on https://klarasystems.com/articles/using-the-freebsd-rack-tcp-stack/ They mention the RATELIMIT option for some network cards but I can find no option of that name in LINT/NOTES so am not sure if it works with just some or all network interfaces or what the tradeoffs are. Can anyone here clarify please? or just point me to whatever I need to look at, thanks -- From nobody Mon Nov 20 14:43:38 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYqyR0Prsz51Nxs for ; Mon, 20 Nov 2023 14:43:59 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (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 (2048 bits) client-digest SHA256) (Client CN "plan-b.pwste.edu.pl", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYqyQ49KTz4LgB for ; Mon, 20 Nov 2023 14:43:58 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Authentication-Results: mx1.freebsd.org; none Received: from [IPV6:2a02:22e0:cf00:1ff:86f5:5b17:8cd7:ba0b] (mzar@[IPv6:2a02:22e0:cf00:1ff:86f5:5b17:8cd7:ba0b]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.17.2/8.17.2) with ESMTPSA id 3AKEhdrG070077 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 20 Nov 2023 15:43:39 +0100 (CET) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1700491421; bh=Y4QVyTHlSm2i2awiuMXyqul0qU2Z1wdtk2hioFz5K+Y=; h=Date:Subject:To:References:From:Cc:In-Reply-To; b=vf+LIFRJfIsLVAM75Jc0VzaGTIsr9ys8e1ZMh/KiRL8tvnuW5h2YaoUngLeBsWrZS qjRJa05kcQoXiN1qXANYW9nDEB8YC9S06wl5iKcS3IcIvopWUaB30ex54BUuQwspDf GUFEWvVS9zw0gcrRS/LGHlNG/csRRvBeFluH+8Rnf3TUEdRRjBIxv3osVEV7cSuja8 rdEFyB/krapANrK1lu9ehTTQUGgN8vDUibjLU3LQm9R6qoNis6jWeA4YSdFYmdi5Eg L//8c2l+bDKEmoRli78JCiu2k6taNMFESx+pCaG97WP/hXaKcyvb2JhK1zThkEh0/F v8nadeo8EtLJg== Message-ID: Date: Mon, 20 Nov 2023 15:43:38 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: the RATELIMIT kernel option Content-Language: en-US To: void@f-m.fm References: From: Marek Zarychta Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; keydata= xsBNBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAHNN01hcmVrIFphcnljaHRhIChQbGFuLWIpIDx6YXJ5Y2h0YW1AcGxhbi1iLnB3c3RlLmVk dS5wbD7CwHcEEwEIACEFAlfi4LkCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQHZW8 vIFppoJXdgf8D9X3VRFSNaR9lthSx/+uqas17J3FJKBo1xMQsC2a+44vzNvYJSuPGLLJ+LW2 HPVazjP/BWZJbxOYpliY4zxNRU0YCp0BLIVLibc//yax+mE42FND/+NiIZhqJscl6MLPrSwo sIwXec4XYkldkyqW/xBbBYXoIkBqdKB9j5j42Npy1IV/RizOSdmvTWY27ir8e/yGMR1RLr4F 8P5K3OWTdlGy2H2F/3J8bIPBLG6FpaIyLQw4dHSx8V02PYqDxK1cNo2kAOnU8PnZL/AGuMOH iv3MN1VYL8ehcmpBBsrZGebQJxrjY2/5IaTSgp9xHYT70kshuU6Qb97vk1mOjNZxgc7ATQRX 4t3DAQgA10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWY hJbA6GK/LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IY a7gk906rktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55 g3+GQ28FvSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapza mV/bxIsaZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABwsBf BBgBCAAJBQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJi v8aogxacQNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3 wh1yMCGBl/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+m u4spKnJ/s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD 1r5P0gxzSqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQb sylq/j672BHXsdeqf/Ip9V4= Cc: FreeBSD Hackers In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:206006, ipnet:2001:678:618::/48, country:PL] X-Rspamd-Queue-Id: 4SYqyQ49KTz4LgB Hello void W dniu 20.11.2023 o 14:46, void pisze: > Hello hackers@, > > I've been looking at adding the RACK tcp kernel option, and reading > the instructions on > https://klarasystems.com/articles/using-the-freebsd-rack-tcp-stack/ > > They mention the RATELIMIT option for some network cards but I can find > no option of that name in LINT/NOTES so am not sure if it works with > just some or all network interfaces or what the tradeoffs are. Can > anyone here clarify please? or just point me to whatever I need to > look at, thanks I am not a hacker, but I have also sought a couple of times what FreeBSD hackers have done with the code. There are a few or even a bunch of undocumented options. Number one for me is still "options RSS". From my experience, the best way to read about them is by digging FreeBSD mailing lists[1], searching on FreeBSD's Phabricator[2] and ... using grep inside /usr/src. If you want to build stabe/1{3,4} with TCP RACK stack then mentioned article published on Klara Systems website provides still right guidance, then both: options         TCPHPTS options         RATELIMIT are required. 1. https://lists.freebsd.org/ 2. https://reviews.freebsd.org/ Cheers -- Marek Zarychta From nobody Mon Nov 20 15:27:04 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYrww5lFCz51Rlc for ; Mon, 20 Nov 2023 15:27:44 +0000 (UTC) (envelope-from deb@freebsdfoundation.org) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYrww418vz4Q94 for ; Mon, 20 Nov 2023 15:27:44 +0000 (UTC) (envelope-from deb@freebsdfoundation.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-9ff26d7c0a6so115827666b.2 for ; Mon, 20 Nov 2023 07:27:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsdfoundation.org; s=gfnp-20170908; t=1700494060; x=1701098860; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yBkOZf21NdykzQmbHyU7ZTEtRYO0NUxa1ResREZ5848=; b=MRr05xUsZ0zaWKO9+MpYCLy5xQoAPa9cK5h7sr+Q67Pwx3zjrah/HpJJSKBjfyGhR2 WaVbJ3gp51zP7k5Sf4Pj9gW9rzN8fet1/ScdwGabtCiEm9VbLtLl13bx8iVF1jPJBAP3 doiycJWPWbSPqH2nnmuDXxxRXPpgQAPlq7sTouTYfXm186xCC4x8uhF2P8EtTHuvyEuY W7eKGoISAju7rcB3UDMWP8u3Gz3g0o1QnfyDmLJOVCLehKxSa/Vtlh4o3pEpCYRCEnx1 qqEAIb6wgjSsUi+QIWsthbo2+7aaQ1xSLP4Z7gnNjMLl/CbE696r2tmNfOFDwDLwXq6u wv8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700494060; x=1701098860; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yBkOZf21NdykzQmbHyU7ZTEtRYO0NUxa1ResREZ5848=; b=Ni/sgACfGJ6oF0rUlQAR0LGkEqGkP0gifkHjXNCMKVvTMLSZHGBcahiXBaJwjjH6xK W15BbMToBXHa6Hvrmg++Ze0XsXD6vube4GIFlnpvihzsmZCwNytUQc+R/GxHxIJoFOc8 Xn0HR3/LaW1OkdLMBzo508QlCIMFkYw16fo+GmzmrFD+6GFqQfpTzFNAf8VRrJEBkX87 N5UFjBkjBKezKbo7TI4qRdusEwohlrfvjZsE97YrH72uLHm5zydcQrEPZbyztVtxDskO yLv6mKrfYcQ2no0RoMkeBgIQKpfc8udePcek2boc7Cvm2ouSS9bW38CtJrdeqWxbB+8C onxA== X-Gm-Message-State: AOJu0Yx3vbjG4aN1VHp3D9jihzsRgnTxc1pNP81I0DEj5HHwB9xLys3j rWQfgHfcs0aftMLioBPc6uwIyHvBzYosSoW97vRu/j9qSEsnM2vDHaU= X-Google-Smtp-Source: AGHT+IGLiuaQn93gxS694KzrM+gABVbqYAOhItgkFVlffdjNg6E3IRifnXEDq0/JMIJMWdCMv4KQn7ZI6lSp1PVp+no= X-Received: by 2002:a17:906:1096:b0:9e4:121c:b9fd with SMTP id u22-20020a170906109600b009e4121cb9fdmr6148792eju.12.1700494060358; Mon, 20 Nov 2023 07:27:40 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Deb Goodkin Date: Mon, 20 Nov 2023 08:27:04 -0700 Message-ID: Subject: Re: FOSDEM 24 devroom To: Paul Floyd Cc: "freebsd-hackers@FreeBSD.org" Content-Type: multipart/alternative; boundary="000000000000691e6e060a972079" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4SYrww418vz4Q94 --000000000000691e6e060a972079 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable The FOSDEM event post needs to be updated. It mentions that it will be in-person again after two years of online events, but it was in person last year. The link to the BSD devroom needs to be removed since it wasn't accepted for 2024. Deb On Mon, Nov 20, 2023 at 2:16=E2=80=AFAM Paul Floyd wr= ote: > Hi > > There's a BSD devroom announced here > > https://www.freebsd.org/events/#fosdem-2024 > > but the link gives "Resource not found" and > https://fosdem.org/2024/news/2023-11-08-devrooms-announced/ doesn't list > BSD. > > Anyone know what is happening? > > A+ > > Paul > > > --=20 Deb Goodkin Executive Director The FreeBSD Foundation --000000000000691e6e060a972079 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The FOSDEM event post needs to be updated. It mentions tha= t it will be in-person again after two years of online events, but it was i= n person last year. The link to the BSD devroom needs to be removed since i= t wasn't accepted for 2024.

Deb

On Mon, Nov 20,= 2023 at 2:16=E2=80=AFAM Paul Floyd <paulf2718@gmail.com> wrote:
Hi

There's a BSD devroom announced here

https://www.freebsd.org/events/#fosdem-2024

but the link gives "Resource not found" and
https://fosdem.org/2024/news/2023-11-08-d= evrooms-announced/ doesn't list
BSD.

Anyone know what is happening?

A+

Paul




--
Deb Goodkin
Executive Director
The FreeBSD Fou= ndation
--000000000000691e6e060a972079-- From nobody Mon Nov 20 15:34:00 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYs4G2F8Qz51RwN for ; Mon, 20 Nov 2023 15:34:06 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYs4F4R46z4R9p for ; Mon, 20 Nov 2023 15:34:05 +0000 (UTC) (envelope-from paulf2718@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=OEA+xrMk; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::42d as permitted sender) smtp.mailfrom=paulf2718@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wr1-x42d.google.com with SMTP id ffacd0b85a97d-32dff08bbdbso3523758f8f.2 for ; Mon, 20 Nov 2023 07:34:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700494442; x=1701099242; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=C6ZFudOvb0OSuvG6mtMIUPxQkS7/PdDtZSCm7ZS/Vkc=; b=OEA+xrMkFCI4tgxQjUtKCet2bk/OSXiDHDx0R8JEHwtsgGuyF/iPplIFTEI75B7/wn F7zLYx0t/7TCfFWhA2URR2PSTv/jrDlOrsP1sotrrzs2NtoC15+7i/3EyRw9XsRmURO6 4zng9hsBAyk6fwJ4UwWAZnDLBADejCP1QMcHTEpL04BU/Untq2SiNONEbwkAjc1ZlUOU d9KALcYGoqWUSlM9h/yK3AgvVMgnniheIS3IU0esambBc8nUxmuTzRop49G19+mz5V+Y +28zq6JpYGYacpKDI6OQpEwjCxKg8aDLlGqaJ9D2qqrSuFps+8ROHKFgrKCOQK8SB+HC ZpgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700494442; x=1701099242; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=C6ZFudOvb0OSuvG6mtMIUPxQkS7/PdDtZSCm7ZS/Vkc=; b=PfZjV/TlVDfd7X+8DKafYXU+SciGkN6Om7GOwmcDUJt4D20CdZcDkai4dtA/daCuvb g6thLVEXzw8WCS8AWBBQiDAYegoLxSXVIxfmFuB0aFjlgyIGM4WpxZMtOA/jbAqsWLmo 0YFXF4uo2iJDLcLyu6ZfSQUlspvkN2zkgdz70ikoMgQBY35nMHNZzWtPPWMc68aGiolb iw4RsjZ614lg+9zBCEUvyWZHqSVLJWqHLuAhVNkn/PaDT+wOWO4JBMY9rJzPVmpi1G5p dkK2iV8mDnCujI8LiDBwXGbBsdf0XMcElCdhIQV2lqUPnxAzMBdtV/wazDLQO+fshzNp sz2A== X-Gm-Message-State: AOJu0YzeFZ2g1azVwexmVL9A7vTJ0FnyFBkcx6Qikt7oKJdYM2MStqp2 f0sTjGZtT60emAp2jeW8O/EoDuf9eHVPyw== X-Google-Smtp-Source: AGHT+IGlqp2FIpT8t5G9b+rAvkhiy27AJB/Dd074hmGERKMB/QoEboG4agnXCvUXKnFaTfSidb57Og== X-Received: by 2002:a5d:4531:0:b0:331:6df2:3603 with SMTP id j17-20020a5d4531000000b003316df23603mr4260388wra.61.1700494442419; Mon, 20 Nov 2023 07:34:02 -0800 (PST) Received: from [137.202.253.23] (nat-ies.mentorg.com. [192.94.31.2]) by smtp.gmail.com with ESMTPSA id cp33-20020a056000402100b00332c6a52040sm4095249wrb.100.2023.11.20.07.34.01 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Nov 2023 07:34:02 -0800 (PST) Message-ID: <40aaca31-3294-4d3d-9b1f-f2ef0f4b2ea7@gmail.com> Date: Mon, 20 Nov 2023 16:34:00 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: FOSDEM 24 devroom Content-Language: en-GB To: "freebsd-hackers@FreeBSD.org" References: From: Paul Floyd In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::42d:from]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SYs4F4R46z4R9p X-Spamd-Bar: --- On 20/11/2023 16:27, Deb Goodkin wrote: > The FOSDEM event post needs to be updated. It mentions that it will be > in-person again after two years of online events, but it was in person > last year. The link to the BSD devroom needs to be removed since it > wasn't accepted for 2024. > > Deb > That's a shame. I was thinking of submitting a proposal. I'll keep it for a rainy day (or 2025) and consider other conferences. A+ Paul From nobody Mon Nov 20 16:03:11 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SYskD5fHjz51TSx for ; Mon, 20 Nov 2023 16:03:32 +0000 (UTC) (envelope-from Joerg.Pulz@frm2.tum.de) Received: from mailhost.frm2.tum.de (mailhost.frm2.tum.de [IPv6:2001:4ca0:2403::81bb:b30c]) (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 "mailhost.frm2.tum.de", Issuer "GEANT OV RSA CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYskD33v0z4WGR for ; Mon, 20 Nov 2023 16:03:32 +0000 (UTC) (envelope-from Joerg.Pulz@frm2.tum.de) Authentication-Results: mx1.freebsd.org; none Received: from mailhost.frm2.tum.de (localhost [127.0.0.1]) by mailhost.frm2.tum.de (8.17.1/8.15.2) with ESMTP id 3AKG3IkW038399; Mon, 20 Nov 2023 17:03:18 +0100 (CET) (envelope-from Joerg.Pulz@frm2.tum.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frm2.tum.de; s=s2048; t=1700496198; bh=gCsd/eAkUFkJ3r1BBKyMCenhifRxRpCb/VYW1M7pPfY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=K8bdNsinI3jzrPGprP5eI7kSw0WWg5TLI0cKLMvdrdVgVe1wjZSiZ3gXKCzM4tkba ktAKutADNplzfubu+0uWUg2qPQGx8xVqVuY5qJWYE4qWs14EATIeP/Mbqog98CEWZs 7C1H9dd3879xVFTde2wMP2f1ZGlaNdtebaa1SqA/pmdZ6l1jTAK4faX0QkmuGxcp+A 72BPzPNZ6VkH7E96xfg2QeuD05rvh0+kBuqK3SDxV4GZOO+Ew9UpE0GKnfsCJcqhCS KaB7nSbz/bFp2kWF/Gjve2JZcGIQHYhd0/iZ9J8hdRoh3zqxrgW3YdO56eh6hW/aW3 DHl/nbvwBMoqA== X-Virus-Scanned: at mailhost.frm2.tum.de Received: from vpn218.vpn.frm2.tum.de (vpn218.vpn.frm2.tum.de [10.155.7.218]) (authenticated bits=0) by mailhost.frm2.tum.de (8.17.1/8.15.2) with ESMTPSA id 3AKG3C27038379 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 20 Nov 2023 17:03:12 +0100 (CET) (envelope-from Joerg.Pulz@frm2.tum.de) Date: Mon, 20 Nov 2023 17:03:11 +0100 (CET) From: Joerg Pulz To: void cc: freebsd-hackers@freebsd.org Subject: Re: the RATELIMIT kernel option In-Reply-To: Message-ID: <77rsnr55-3670-1614-no91-172ns786n2n2@sez2.ghz.qr> References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="419043047-695649499-1700496192=:95300" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (mailhost.frm2.tum.de [129.187.179.12]); Mon, 20 Nov 2023 17:03:12 +0100 (CET) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12816, ipnet:2001:4ca0::/32, country:DE] X-Rspamd-Queue-Id: 4SYskD33v0z4WGR --419043047-695649499-1700496192=:95300 Content-Type: text/plain; format=flowed; charset=US-ASCII On Mon, 20 Nov 2023, void wrote: > Hello hackers@, > > I've been looking at adding the RACK tcp kernel option, and reading the > instructions on > https://klarasystems.com/articles/using-the-freebsd-rack-tcp-stack/ > > They mention the RATELIMIT option for some network cards but I can find > no option of that name in LINT/NOTES so am not sure if it works with > just some or all network interfaces or what the tradeoffs are. Can anyone > here clarify please? or just point me to whatever I need to look at, thanks See src.conf(5) WITH_RATELIMIT and ifconfig(8)'s txrtlmt. Further details in sys/netinet/tcp_ratelimit.c Joerg --419043047-695649499-1700496192=:95300 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: BASE64 Content-Description: S/MIME Cryptographic Signature Content-Disposition: attachment; filename=smime.p7s MIIK8wYJKoZIhvcNAQcCoIIK5DCCCuACAQExDzANBglghkgBZQMEAgEFADAL BgkqhkiG9w0BBwGgggdKMIIHRjCCBS6gAwIBAgIRAPbF0FqkCfgJVL93Ywop ZXswDQYJKoZIhvcNAQEMBQAwRjELMAkGA1UEBhMCTkwxGTAXBgNVBAoTEEdF QU5UIFZlcmVuaWdpbmcxHDAaBgNVBAMTE0dFQU5UIFBlcnNvbmFsIENBIDQw HhcNMjMwNjIxMDAwMDAwWhcNMjYwNjIwMjM1OTU5WjCBrzEOMAwGA1UEERMF ODAzMzMxKTAnBgNVBAoTIFRlY2huaXNjaGUgVW5pdmVyc2l0YWV0IE11ZW5j aGVuMRgwFgYDVQQJDA9BcmNpc3N0cmHDn2UgMjExDzANBgNVBAgTBkJheWVy bjELMAkGA1UEBhMCREUxEzARBgNVBAMTCkpvZXJnIFB1bHoxJTAjBgkqhkiG 9w0BCQEWFkpvZXJnLlB1bHpAZnJtMi50dW0uZGUwggIiMA0GCSqGSIb3DQEB AQUAA4ICDwAwggIKAoICAQCiaVZz+s4NMNG2UK88TWxTgAq8oaABH0lUEpMq wF9qQc96GmTpsOwhKjiqkeGe36Vaq1b7NNTdGgBabyP+p2R4bDySkUxGQHzK p2mZauZ4VFLZWMoy2QJf1Q02t33RQzjnpt0aQWR5/sF/zfkL31Tj5b9iTTNZ Ixxr2SNZXuM/+iFNLvVp42IFHi856RIGEhcrlSHmcnGE1DmSZY/kQV+y9zWJ 50lIoMK38eVDWD07XSG8LSLZEx4ckR7VSUKVH7JN/ZOFTZJwzWe1B4KAiTCk NRs9S3x/hR/x/C3b4Kc6tbBgY+C9eri1b1AO1jG/mnoCUSjFy9K/bQYcNKaf cw9QA1mZ5rAysX+6dFyNbBaAucsPpUAJPdagLDpSWvIcmgrlDudRuyqyEybL H/YEW35gbK2LbLJFQJyH9F7cGahjMWGvEOb+9cpOy4tFMWYa8ANH4u/yA/gq X+9R/vE7uuqm7geqfRvgURLsChtfvpT+o19RY77sGjfnZk+rBX9Y6mxITfJB 6O9Zl5WFvsjBD4ZUV9LhJC2HlNXmitdsXpvvO10mQ95klPHivbwj0OpAC0Fe LTJCw23psyDLRfQDmXcRh2O1UXJgcg2ADc2RaMfkqAcrWrvmZfh6Ph+6vnbq 06weCfPMxZll4vijt+nM8CfZLG7BSAs39I7uoSHd/3ZOHwIDAQABo4IBwzCC Ab8wHwYDVR0jBBgwFoAUaQChxyFY+ODFGyCwCt2nUb8T2eQwHQYDVR0OBBYE FG2a3unKDH7C8Gll3Ac4lXKTo19/MA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMB Af8EAjAAMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjA/BgNVHSAE ODA2MDQGCysGAQQBsjEBAgJPMCUwIwYIKwYBBQUHAgEWF2h0dHBzOi8vc2Vj dGlnby5jb20vQ1BTMEIGA1UdHwQ7MDkwN6A1oDOGMWh0dHA6Ly9HRUFOVC5j cmwuc2VjdGlnby5jb20vR0VBTlRQZXJzb25hbENBNC5jcmwweAYIKwYBBQUH AQEEbDBqMD0GCCsGAQUFBzAChjFodHRwOi8vR0VBTlQuY3J0LnNlY3RpZ28u Y29tL0dFQU5UUGVyc29uYWxDQTQuY3J0MCkGCCsGAQUFBzABhh1odHRwOi8v R0VBTlQub2NzcC5zZWN0aWdvLmNvbTBBBgNVHREEOjA4gR5Kb2VyZy5QdWx6 QGZybTIudHUtbXVlbmNoZW4uZGWBFkpvZXJnLlB1bHpAZnJtMi50dW0uZGUw DQYJKoZIhvcNAQEMBQADggIBAGQnoiV3hYZSlcgpxSvVHdhUk2N9COKh3BdJ WDTCVHyiRcoh9Ubwi8nirC/ywZtv6CL6ipspfoW747Y5svxaigMWgDGRH6H5 OlkuhRl+3O2glz/X2yMxWywbyI0A5jpEp2LSRSSyo5eDyZAIwEkoDzlGjLu7 dMgWQXAR/oya2nLoawpVI1Ji6NUeqNwXXiAI04Fu1JdUHw6S0xAifmnPy2CK MZj0N+8Z+CKLoDF8IlijZ8rlABY9jZSsrbsvZtUUr9W4s1YPPsBfqBvn3IPH UHC7dLJNWjurm1ouW116aYH8ny2hD55s+xoix45Q3tV4LnKrhe0OE9l82kwq mpYgqyBfmdqGx9MNCzbt5cGM4oVJlXsAmn/MRIPHBE65VvOJYKMsLR0zFu8H /rxD2FqixojlO2qPKp5Psyp8vkFfgct58szXhvS/baSTFCogZyq1nNrjU3lD YzkfzB6TPutFzdAPE0kG21Vj//lfyey/Dt/s1jlgPJMUoSHxqlaKV8fsGKcP TlIGztCrPIW0LA4q+y5/atJDcGEumUl/ZWAOdtgWJ8Vs99utaWMh31aZRrYR LuugOekI8P9dMMsPXWek1NK57PJ8oWBmQ5q4ME7NYLeBm4ku2mrdmTba4ejl oWkl23NSP+3Y7ifTHp18PcKtvkCK9c2IR8LscF6wHSfvROEbMYIDbTCCA2kC AQEwWzBGMQswCQYDVQQGEwJOTDEZMBcGA1UEChMQR0VBTlQgVmVyZW5pZ2lu ZzEcMBoGA1UEAxMTR0VBTlQgUGVyc29uYWwgQ0EgNAIRAPbF0FqkCfgJVL93 YwopZXswDQYJYIZIAWUDBAIBBQCggeQwGAYJKoZIhvcNAQkDMQsGCSqGSIb3 DQEHATAcBgkqhkiG9w0BCQUxDxcNMjMxMTIwMTYwMzExWjAvBgkqhkiG9w0B CQQxIgQgaBclY+IUMOAp/lRCf2xdh5vU7xR/6+fvOVYM9cogYAMweQYJKoZI hvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFl AwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwIC AUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggIA CJ4paTjf4OScQ/We4a65We6Gzt4O4Ps5gUNFUVsU9BdEwZs/fFHpYLkEMzZp Eky0XYsWQEnQy36ShLFrPwyoFZdzwzvt2c5q+RhPevmowDGNcoDIZo8/n/LE DBAj+GIcuoo4LC9cYfJ5Fr0KmcERmPQiEiO+h48KpuXWDbQzg9STjQwVyIf4 Rhc/mv88E6tCx4FpdEN6bxvikY+YU6WNdIO6T4/j0ipsi4XRulALyL5b9vE+ 90bKJX1f9lYF6vCa5aiSfMs8dro733shT94wvfyYmWKbePr8P/DTYJAVzW2w dZgGvitW1S0l6QSSdmLNgP2nc7CsrkaQz9Dt24hOdjqA9ZEZaxCYw4a3BNoD YJ/waeCNbywn1f13F4pcNslr2aMsdk03apu/EvbuaLJsDPkuJL96BvUVjpHX f8S2T70y6w46W1B7kvA4mHSXXiCJYGSk1Kfnv/BPWKN2HVu3iYmagjNB7mT8 sf0aGS13v64T1g8yRWtOueiBMoctpBoqLvjvPMiGpJokqQQek2FZutu04CU0 w4ni7eIs47uAO3QvsXafCRpgGJOObqwQG2wG80Ma55RnHlChslrLwCaEec4d +ItZSDb5/oMz+JroSi7B4lDzmjshVHBGBExsTAVlgFn/6jN21VlCjcSEudB6 sodz0B6BJ5BDjp4t4F3vLUM= --419043047-695649499-1700496192=:95300-- From nobody Tue Nov 21 03:23:48 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZ8qF1zZCz51dh3 for ; Tue, 21 Nov 2023 03:23:53 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 4SZ8qD43krz3Mlm for ; Tue, 21 Nov 2023 03:23:52 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b="PBLTl/WC"; dkim=pass header.d=messagingengine.com header.s=fm1 header.b="e PwSgDM"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 257883200E0F for ; Mon, 20 Nov 2023 22:23:51 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 20 Nov 2023 22:23:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1700537030; x=1700623430; bh=zEa+w1LGT6U80PPc0tTt+n0YHfdwjPDy+v2 hZVEasyU=; b=PBLTl/WCkx040pSiZaECdSmEydFn/0D5+aoP3dHwSqSajxkRzGW v/s5DvUb68PkJKBvLSRDdu6dMtf9nkqHt9JG3JnEn6Rt2/7NMrTxo6oMsrXCGfBo rubs2YKeh10o/aSyRa5Qgevhnfj5Bq2y4C9ytEXCNche98gJrTB4UN1EskvhDDJv LuRiyax3lCSOQxNXaOMNeeGr6sr3/lF3u4Xk6FYXlvn2vBZI3mAwhMvVIQcjYxxv 23yNKLY1FHUzeU1sMQL1c7uEyoSUM518yjvkkflvJXjQ9sBEIC+0mhfG6GZI/oIR YYbrqOSbKB8CPaby7OqjmZlQGJcULCdn9gw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1700537030; x= 1700623430; bh=zEa+w1LGT6U80PPc0tTt+n0YHfdwjPDy+v2hZVEasyU=; b=e PwSgDM/fyXnYwdij9cGewDSSAxmwU84G6QKcBm18Q8fjqYxm7ruhzlPRvfap8Qic QFr7M4CIQjSmN7CDQohDyn3YCji7AJirkC4+Dy24Sb64psC5ilsQHPhH6dlwJq+p LJPp+U6fWgxQGpGroQ1Xqom7JlcWtDVdXOsRPQjqAhrHOAn4X2tDNf6NOcilzB/s nLS6Q9za6E0DbCLK/P1dnc+z/co4HUQRBUvdBQUcrfVqG8lDs3qHJw+nPaWC6rBK 52Pzh2dmubhIMOaKr9KqDkC499cr/djSvFu7OHBAdtDVqv1x5ANhmoYG1UTbYnYS pswBgY+XvjR5Mb7uJ1tcA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudegkedgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtke ertddttddunecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpeekvdejiedtjeehkeeikeekiedutdffvdduteehveegieejhedtffefge egkedtfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 20 Nov 2023 22:23:50 -0500 (EST) Date: Tue, 21 Nov 2023 03:23:48 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: the RATELIMIT kernel option Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spamd-Result: default: False [-5.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.24:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SZ8qD43krz3Mlm X-Spamd-Bar: ---- On Mon, Nov 20, 2023 at 03:43:38PM +0100, Marek Zarychta wrote: >Hello void > >W dniu 20.11.2023 o 14:46, void pisze: > and ... using grep inside /usr/src. yep, thats what I should have thought of I'm just interested to learn how and where the option works. I'll edit the kernel config like you & the site mentioned. There's a few NICs and devices where RATELIMIT is mentioned specifically: sys/contrib/dev/iwlwifi sys/dev/cxgbe sys/dev/mlx4 sys/dev/mlx5 sys/dev/wg sys/net/if_lagg.c sys/net/if_vlan.c sys/netinet/tcp_ratelimit.c sys/dev/qlnx/qlnxe/reg_addr.h -- From nobody Tue Nov 21 03:26:33 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZ8tP3MW3z51f8V for ; Tue, 21 Nov 2023 03:26:37 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZ8tP05hHz3Nr3 for ; Tue, 21 Nov 2023 03:26:37 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=LhDyFxdp; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=RHnaFwTp; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id F1C6F320099A for ; Mon, 20 Nov 2023 22:26:35 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 20 Nov 2023 22:26:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1700537195; x=1700623595; bh=00 e1HbeOZjtHesnJzLBwkWrZmN4bsRSJG0SxBL8ohUk=; b=LhDyFxdpGotMfmTh/4 HNi2s9nRKMBF+YS1LYelj6VBDE4UTe7CEGkXRssq47RtDZ4JoUf85JJRHcrEgsQO 8mcoKPAWsuxe7+otSEHuRI5BRCSJ6ahyEugoU/55g235BBUGLoPr0SU9vPfXii0m e+CzSxlYt+OGRzgjtI3hGqwBlXazupv+o1YBr74IeR+sqkK9cS5mCnSNt5FBXx/c tXRf9VO2u3A4TGX3sd/Ilgt9nncJLtuxS+s5//u7jcP8V1+bLsgYA28AF+oIgvKW iNKbct9qJCg2LdH6c3aZD5tupkt7Yp1WiopfXIO/eEVVCdQMFy2zjx4PefDRIRsm DYBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1700537195; x=1700623595; bh=00e1HbeOZjtHe snJzLBwkWrZmN4bsRSJG0SxBL8ohUk=; b=RHnaFwTpl4a7dD4xIlbWpp7S4Ri4M XXVNJRol/y3dG2lIMzBFmyBWlceF5Bye1ok+HF35oRh8M/XrK5Rn0T4dORXshInL 2JYX/KZXsg0pAmzN5L6DNjK3aN8phnNoR+xxQWViDUKZwB8qbsz7mD+08NBrvbEd aas84ss7cF5pkBVDee+qQE/98+oSIBYnYEtjdb4i7v/01rljAQe3g0i8QEzr34GO oXNpdcftZUiDvMgI/4c9uU9SK1ZymNxINbV9D3rMsn6zRrZU60gaF98lgSSVb6mQ eersdOG6s770oJl5CYCobBQJngsXfmLDG2iM8h0Z3iMGDga27Bine4juQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudegkedgheelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepkeeluddvlefhieelfefggffhffektdehleelgfdugfdvgeekjeejuddthe ehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 20 Nov 2023 22:26:34 -0500 (EST) Date: Tue, 21 Nov 2023 03:26:33 +0000 From: void To: freebsd-hackers@freebsd.org Subject: Re: the RATELIMIT kernel option Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <77rsnr55-3670-1614-no91-172ns786n2n2@sez2.ghz.qr> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <77rsnr55-3670-1614-no91-172ns786n2n2@sez2.ghz.qr> X-Spamd-Result: default: False [-5.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.24:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SZ8tP05hHz3Nr3 X-Spamd-Bar: ---- On Mon, Nov 20, 2023 at 05:03:11PM +0100, Joerg Pulz wrote: > >See src.conf(5) WITH_RATELIMIT and ifconfig(8)'s txrtlmt. > >Further details in sys/netinet/tcp_ratelimit.c thanks, thats what i'm looking for -- From nobody Tue Nov 21 10:51:22 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZLmN4Fxvz51N59 for ; Tue, 21 Nov 2023 10:52:04 +0000 (UTC) (envelope-from dr3mro@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZLmM5MXRz3Gv8 for ; Tue, 21 Nov 2023 10:52:03 +0000 (UTC) (envelope-from dr3mro@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=F6Y5vhSJ; spf=pass (mx1.freebsd.org: domain of dr3mro@gmail.com designates 2a00:1450:4864:20::533 as permitted sender) smtp.mailfrom=dr3mro@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-53e2308198eso7644058a12.1 for ; Tue, 21 Nov 2023 02:52:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700563921; x=1701168721; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=1LrXU4aTTMiri6pY6Nj5JaiqkTEpzfvf99uJ7focWbw=; b=F6Y5vhSJt07op+yK8YWWrYE/yAaOGwKjUWgJlXpjNA3xoc5PYMKbWb+AH70UaIN6Zg CBom423DJxQ5g3LbTHB8pmAzrI/oB0OoY4d/B8mrv7R1ZsSkRpXokh2Qt8s6ZK3YeKM3 3Vdg0m9BCsfg/34i6tr3OrXfPuQU36/xndAX8DR/y1NuaiVuSEeB/eUZRIb9VxVLg3N4 poMzzeICvfE2JBpyjVW42yowgAmCjSD/GUbD/0rqOUUjUxt57ZYy9TEMV6mfY2HyPJso GuSXs6ySIYtEHvd4CYD8A1UEmyVhf6b071+ekvhgWhLeQ8BQt8mc6QtuFnYZacq5Fy6A KgMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700563921; x=1701168721; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1LrXU4aTTMiri6pY6Nj5JaiqkTEpzfvf99uJ7focWbw=; b=MnO90+lfQLvxNXiiW2z6nLJczMVDtyh7RuV7Xo1Fh6oS4lC2TYA7E//J5qts1t/sv0 f8GD0TkHcC7U6Dc2DJ28SBpw6IVp1iz9c9EX7e6QEy2Bn3Gj7IlbG9GRyVyJMuFU6MYZ +JCy76xxl/ME3asimGZ00dgxx+VqSP+TaSUzARXl8ZOjfdwVx5+V7yPI3oKLKJq23MYC v7CniLXpzbvwPPud4Ib8hmQuEBTX36nBl/BzA3CySDFBhh6kFmtAjV+6eQtkHc2UuO+d z4C7ljTf5A5BJ7cPrr9KTvOt+e3JtLgR1BcjVv1sQ7fRApZvJomloKrCVciZpGIKJv8T gxKg== X-Gm-Message-State: AOJu0Yyoz9U0uJQSO1R0+VIb27DJPPhWZCkm40r+1v5ztBRA8OfKe7d5 WqRpv9B6S0hywyHdsTyUwg7659fHfGl0BCjBrMekcvQf3qKWhA== X-Google-Smtp-Source: AGHT+IELHhN4N1JlzosRatknbujLVqk8pbz4R/p82VyyHRjcdg7o3CNTHhBDlZz7wwtQS+OLrkOpB2sZMxlG6wZ8pJs= X-Received: by 2002:a17:906:2c07:b0:9ef:e6fd:fe5a with SMTP id e7-20020a1709062c0700b009efe6fdfe5amr7034614ejh.74.1700563920397; Tue, 21 Nov 2023 02:52:00 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: "Dr. Amr Osman" Date: Tue, 21 Nov 2023 12:51:22 +0200 Message-ID: Subject: issue playing video using mpv To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-3.00 / 15.00]; FROM_NAME_HAS_TITLE(1.00)[dr]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::533:from]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Rspamd-Queue-Id: 4SZLmM5MXRz3Gv8 X-Spamd-Bar: -- Hello, I have freebsd 14.0-release with xfce 2023Q4 the issue is when I start video playback using mpv I get the video full screen in another tty and if i quit I will be on the empty tty and I have switch tty to return to desktop it wont work in window mode except if I set vo=x11 after a fresh boot it works fine for the first launch only which might indicate its a software bug not related to my config I Use thinkpad x270 with intel 620 gpu and i915 kmod from the ports tree (2023Q4) here is the terminal output --- (+) Video --vid=1 (msmpeg4v2 720x480 29.970fps) (+) Audio --aid=1 (mp3 2ch 44100Hz) libEGL warning: DRI3: Screen seems not DRI3 capable libEGL warning: DRI2: failed to authenticate [vo/gpu/opengl] Suspected software renderer or indirect context. [vo/gpu/drm] VT_GETMODE failed: Inappropriate ioctl for device [vo/gpu/drm] Failed to set up VT switcher. Terminal switching will be unavailable. WARNING: Kernel has no file descriptor comparison support: No such file or directory AO: [oss] 44100Hz stereo 2ch s32 VO: [gpu] 720x480 yuv420p AV: 00:00:02 / 00:01:00 (4%) A-V: -0.000 Exiting... (Quit) [vo/gpu/drm] Failed to commit ModeSetting atomic request: Invalid argument [vo/gpu/drm] Failed to restore previous mode -- Thank You Dr. Amr Osman From nobody Wed Nov 22 04:42:22 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZpWP22wZz51mwM; Wed, 22 Nov 2023 04:42:25 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZpWN1q7jz3dwm; Wed, 22 Nov 2023 04:42:24 +0000 (UTC) (envelope-from grarpamp@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=GAz0pRpR; spf=pass (mx1.freebsd.org: domain of grarpamp@gmail.com designates 2607:f8b0:4864:20::e2f as permitted sender) smtp.mailfrom=grarpamp@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-vs1-xe2f.google.com with SMTP id ada2fe7eead31-45d9689b65dso2154115137.0; Tue, 21 Nov 2023 20:42:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700628143; x=1701232943; darn=freebsd.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=8/9epigCmT7oLEq+fiQ1sdwGqWB5XIGaEKdAjxsvX6I=; b=GAz0pRpRuo+OIN+C9doT53UnF4duUc0wqJTu2hKNb+3gmcPH5k5ZOQXwYmH4TMj1F9 Pw1zqMLQ+Ms5upz8ODUjHuy9sfT/KqjdFdjyA/jzh1Wl6rHnw/upBqVXxcxrpYa+lJQk c0ne0j6WaGbIs+HQOxH3FWCIJJjuAxihyd+4sHUcTKYbecywI2qu8qQ947iYljRjhFfj J4UXjksvJt1ce+2mqR8jx8z/SI4p7IvSu0eAjpBj0O/aHMi3saZO/VWkBcMp8EMMUG2p a9WESWKE8G1s6pNeipefbrfEF/Pa/jr7JeAFHLe1j5LbyziaerNLWttrJW8iV+36sAMo RWKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700628143; x=1701232943; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8/9epigCmT7oLEq+fiQ1sdwGqWB5XIGaEKdAjxsvX6I=; b=jbz3peY3xuEaTN2FtYfxh8FRYc94WTC/SNKEzda5fV5UFT4/ta6OBP89FTP7QtSWdd opbmZs/LzOGtd+z/CHI5xiXiahQKonwwe9McMGNGuR+hkO6dC+OnusODp0xrBFTJhL90 iHaHoVS6wOYIfUeSl8A/zRm8Z+6yk3xqr7cnOSvHngJTc54Sz7QJMtSb93niB15Bgs/g a2O+m6qPCdU+Oj0jMX1kgc6GOdU+xAp6VNYdwcdsauUrh1/oCLvvEV71x5g6uqFEATY9 Sb4DZKugHOmk9oOWEWA+2L3J6Jt5u0Hoz7WiPmNTgxnaEX97COj50qBxedobJkJHA1fV dqKQ== X-Gm-Message-State: AOJu0YzYmxHoMnIZT7qXt/hRkwvZEYWEMuNpVcofgg7SpFYY8oIJDqV1 IGTBrTIpZuhaU7HE2ZMdgJt472wfxBzDovh9BpgmRu8ruCS/MeBy X-Google-Smtp-Source: AGHT+IHvD+OAwVjM/oZtgtjSUh5hlC8RagY5/bAkTNUgZjJCkW1rS154FpTKpDzYkutf6W29P0m/ZPQ2Y8dCTvBofFM= X-Received: by 2002:a05:6102:4421:b0:45d:9113:328b with SMTP id df33-20020a056102442100b0045d9113328bmr1622984vsb.24.1700628142935; Tue, 21 Nov 2023 20:42:22 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Received: by 2002:a05:612c:791:b0:434:4f32:1aa with HTTP; Tue, 21 Nov 2023 20:42:22 -0800 (PST) From: grarpamp Date: Tue, 21 Nov 2023 23:42:22 -0500 Message-ID: Subject: Cryptocurrency, FreeBSD, and on Phones could all Benefit Together [was: poor documentation] To: freebsd-questions@freebsd.org Cc: info@freebsdfoundation.org, freebsd-jobs@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org,freebsd-jobs@freebsd.org,freebsd-hackers@freebsd.org,freebsd-hardware@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e2f:from]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4SZpWN1q7jz3dwm X-Spamd-Bar: --- [re was: Well, no entity in the world has ever made perfect docs that cover or teach everyone everything, not possible :) And FreeBSD has recently been making some good major updates across its entire documentation space.] And now there are some new possibilities that some entities are beginning to embrace to see what works... FreeBSD has the power to serve cryptocurrency nodes to the world. Indeed, it serves up some crypto nodes, some crypto corporations run on it, some crypto client software is run by crypto users on it, etc. So if FreeBSD community would like to improve documentation, hardware support, desktop, features, consultancy services, educational and howto media channels, and more... Perhaps they could consider for some things there... - Posting up on the worldwide crypto job boards. - Running crowdfunds, prediction markets, bounties. - Setting aside some portion for a crypto endowment. - Enabling crypto donations, sponsorship, referrals, etc. There are a lot of potential crypto funders out there who like opensource but can't send tips and sponsorship to FreeBSD and community because they still don't accept crypto. Reaching out to and engaging with the crypto world, porting all the popular crypto coins client software to FreeBSD, getting mutual awareness adoption and cross-marketing going between FreeBSD and the Crypto Scene, can all help bring new resources and ideas and users into some of the areas you seek to address. Those job boards could even yield a new job in the crypto space, then you could donate part of your pay to those working on FreeBSD in the form of cryptocurrency. Partnering with the crypto community could also be perhaps the fastest way to fund getting FreeBSD ported and running as the OS on an opensource crypto phone. A lot of the Crypto Scene don't really trust their Google'd Apple'd OS as a good idea on their crypto phones and are looking for an alternative OS, especially given devices like PinePhone, Librem, etc are coming out. Take a look at how hardware and software and the crypto scenes are coming together to accomplish things. And at how entities and non-profits, and individuals are accepting and using crypto. Consider recognizing the advent and power of cryptocurrency and working that greenfield to build mutually beneficial ecosystems. After all, cryptocurrency is the future, and those who are integrating some of its models would be well positioned to prosper in that future. Happy hacking :) -- YouTube search: xWAwK2fHArc , _U3lEc-IFr8 , ... https://duckduckgo.com/?ia=videos&iax=videos&q=voluntaryism https://odysee.com/@Anarchast:2 https://bitchute.com/ || https://rumble.com/ || https://odysee.com/ X.com: NameRedacted247 || Rumble.com: v3x4ssy https://libertarianinstitute.org/books/voluntaryist-handbook/ #OpenFabs , #OpenHW , #OpenAudit , #FormalVerification #CryptoCrowdFunding , #PredictionMarkets , #OpenTrust #GuerrillaNets , #P2PFiber , #GNURadioRF , #PrivacyCoins #DropGangs , #CryptoUAPeez , #DistributedEverything , ... From nobody Sat Nov 25 11:41:03 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Scqgp4tp8z52FHM; Sat, 25 Nov 2023 11:41:42 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Scqgn5Cnzz4Vnh; Sat, 25 Nov 2023 11:41:41 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=hoiORWyH; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2a00:1450:4864:20::534 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-548f0b7ab11so3744841a12.1; Sat, 25 Nov 2023 03:41:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700912500; x=1701517300; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=azjIXGhUpx8mRf9YywHFybitCenT4RIf9yxVGY4Q2P0=; b=hoiORWyHZ5ZxPXQkm9pn65hjiDLuv7C/MJ+Vxz5xypdrXDMwnzlV8JWaI53IszeI+x sJDEygaYXlOkCGV/PCWqekyH627QP09CegAcO9Fc1Mxqp781bWofyG43JTwTUyoEAqDr iUnRBD0uOuopLKrfNdJonaBS8MtKD4p3NaBqvS7BjiFKDYAXZJTmMy4HOFCG+6jtbJIT qSOQGpn9Mo/Xk/yIV6i/d1853ykmlW0fHsQPbO+M8+fRvpKFXV8Bsm3NWnbMcb50kTcj 5L/IgqnD6wN1Ksx4HkARTgp+HCsPA7dHA1Q2xJVZUxbvY9H1NtHAOxNi6fRZ/iExKBQc goTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700912500; x=1701517300; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=azjIXGhUpx8mRf9YywHFybitCenT4RIf9yxVGY4Q2P0=; b=vW1Is14FHhJjV0zzIrmZvrhJ11v5iETF1ImEnukYrtwYoDKjJJ7UToOeRfHBLqhFT2 ANl4vj8X+RHgBcvoiwfbJtJR53NTOE1wSc12MpMZaIhZJnQujozrGqpi82Tt4glIe/ov qpk+K5VdlXjQXDqY86kIkfjg0K8oK/hO87Dk+AYv3ZPZBSJBKSY7JZWstRInkhgeLsWL T5q4uLuPsNULsFKjC4V4wZf+xPf1QCEcvogWl4VPnV3uqflR+qxhbRCOLqVkmJygHIbN Q9Q/ulFue3MBCXgJG263suEISC2K8X98l4h9IKSz9WPytRrh9CNI60Y+W8/Uxru6LaVA iuqw== X-Gm-Message-State: AOJu0YzO05HLZ5j3VJQfFJZVZoGmeHBUQse1MK6iXGWzzXWvR+4THN30 v0VuaTWrFjJldNB0EGVQDbe5cUMif6pn7zNx+SeVVh1eTvo= X-Google-Smtp-Source: AGHT+IGpCIUAyjFh3G2HUz4/okVYKzia3wH/NAaFC75uH5L3c2mUsSVPHkOyuVI0/FhJpw74VS3WFG/LcW4W1pbsWhA= X-Received: by 2002:a17:906:15d:b0:a0b:6d32:2e09 with SMTP id 29-20020a170906015d00b00a0b6d322e09mr1386684ejh.36.1700912499758; Sat, 25 Nov 2023 03:41:39 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 25 Nov 2023 12:41:03 +0100 Message-ID: Subject: Fwd: Should we boot the FreeBSD kernel in ELF format or in zImage format ? How? To: freebsd-hackers , freebsd-arm@freebsd.org, FreeBSD Current , FreeBSD Mailing List , freebsd-xen@freebsd.org, royger@freebsd.org Content-Type: multipart/alternative; boundary="00000000000057995f060af88d0b" X-Spamd-Result: default: False [-2.48 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_HAM_LONG(-0.85)[-0.854]; NEURAL_HAM_MEDIUM(-0.63)[-0.626]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::534:from]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-arm@freebsd.org,freebsd-current@freebsd.org,freebsd-questions@freebsd.org,freebsd-xen@freebsd.org]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4Scqgn5Cnzz4Vnh X-Spamd-Bar: -- --00000000000057995f060af88d0b Content-Type: text/plain; charset="UTF-8" Hello to everyone. we have just virtualized Debian 12 on our arm (32 bit) Chromebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's work was not accepted upstream by FreeBSD, we will have to find his patches and apply them ourselves to the FreeBSD on arm kernel. We found these slides : https://events.static.linuxfound.org/sites/events/files/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what we want to find. It looks like when that slide presentation was written, there were some limitations on FreeBSD Xen guests. For example, for our debian bookworm guest, I am using vcpus = '2' to match the number of real cpus on our Chromebook, but slide 13 mentions support for only 1 VCPU with a FreeBSD guest, so I will need to change that vcpus = '1' in the FreeBSD guest config unless support for 2 or more vcpus was added later, which is possible because that slide presentation is 9 years old. Here is where I would expect to find the XENHVM FreeBSD on arm kernel config file: https://cgit.freebsd.org/src/tree/sys/arm/conf But it is not there unless I am not understanding something correctly. For now, unfortunately conclude that the support for Xen on arm that Julien Grall mentioned in that slide presentation 9 years ago was never added to the official FreeBSD source code. I am searching the web now to see if the patches that Julien Grall wrote are still posted somewhere online. If we cannot find them, we can ask here and on the xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the patches if we cannot find them online. According to this page from the FreeBSD wiki: https://wiki.freebsd.org/Xen I think FreeBSD only supports Xen on x86, not arm. So this is going to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past ! I found a slightly newer slide presentation by Julien here: https://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd It is about the same, but it mentions the GENERIC FreeBSD kernel supports Xen on arm64, but still says we need the XENHVM FreeBSD config for Xen on arm 32 bit, which I haven't found online yet. Please,take a look at this output of the linux kernel that can boot on Xen, and the FreeBSD kernel that cannot : % file zImage-6.1.59-stb-xen-cbe+ zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little-endian) % file FREEBSD-XENVIRT FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not stripped The FreeBSD kernel that won't boot is in ELF format but the Linux kernel that does boot is in zImage format. I spent time reading the docs on xenbits.xenproject.org, and according to those docs Xen on arm only knows how to boot a kernel in the zImage format, so the FreeBSD kernel is in a format that modern Xen incorrectly detects as an x86 kernel. I also watched Julien Grall's 30 minute video presentation of his work to boot FreeBSD/arm on Xen at FOSDEM 2014 here : https://archive.fosdem.org/2014/schedule/event/freebsd_xen_arm/ In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting occasional crashes and needed to investigate the problem. He mentioned the zImage ABI that Linux uses, but pointed out FreeBSD does not use that format, and back then it was an open question which format to use to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only supported format is still the zImage format that Linux uses. It looks like Julien's work back then was using an ELF binary to boot FreeBSD/arm on Xen instead of the supported zImage format that Linux uses and the modern Xen toolstack exits with an error when trying to boot the FreeBSD ELF formatted binary that Julien's patch creates. So the best solution would be to try to port the rules to build a FreeBSD kernel in the zImage format instead of the ELF format. I have been studying the Makefiles in Linux to see how Linux builds the Linux arm kernel in the zImage format, but it is not trivial to understand. -- Mario. --00000000000057995f060af88d0b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello to every= one.

we have just virtualized Debian 12 on our arm (32 bit) Chr= omebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It=20 works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm=20 guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by= =20 FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we=20 enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's wor= k was not accepted upstream by FreeBSD, we will have to find his patches=20 and apply them ourselves to the FreeBSD on arm kernel.

We found these slides :

https://events.static.linuxfound.org/sites/events/file= s/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf

Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what = we want to find.

It looks like when that slide presentation was written, there were=20 some limitations on FreeBSD Xen guests. For example, for our debian=20 bookworm guest, I am using vcpus =3D '2' to match the number of rea= l cpus=20 on our Chromebook, but slide 13 mentions support for only 1 VCPU with a=20 FreeBSD guest, so I will need to change that vcpus =3D '1' in the F= reeBSD=20 guest config unless support for 2 or more vcpus was added later, which=20 is possible because that slide presentation is 9 years old.

Here is where I would expect to find the XENHVM FreeBSD on arm kernel co= nfig file:

https://cgit.freebsd.org/src/tree/sys/arm/= conf

But it is not there unless I am not understanding something=20 correctly. For now, unfortunately conclude that the support for Xen on=20 arm that Julien Grall mentioned in that slide presentation 9 years ago=20 was never added to the official FreeBSD source code. I am searching the=20 web now to see if the patches that Julien Grall wrote are still posted=20 somewhere online. If we cannot find them, we can ask here and on the=20 xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the=20 patches if we cannot find them online.

According to this page from the FreeBSD wiki:

https://wiki.freebsd.org/Xen

I think FreeBSD only supports Xen on x86, not arm. So this is going=20 to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past !

I found a slightly newer slide presentation by Julien here:

https://www.slide= share.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

It is about the same, but it mentions the GENERIC FreeBSD kernel=20 supports Xen on arm64, but still says we need the XENHVM FreeBSD config=20 for Xen on arm 32 bit, which I haven't found online yet.

Please,take a look at this output of the linux kernel that can boot on X= en, and the FreeBSD kernel that cannot :


% file zImage-6.1.59-stb-xen-cbe+
zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little=
-endian)

% file FREEBSD-XENVIRT         =20
FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dy=
namically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not=
 stripped


The FreeBSD kernel that won't boot is in ELF format but t= he Linux kernel that does boot is in zImage format.

I spent time reading the docs on xenbits.xenproject.org, and=20 according to those docs Xen on arm only knows how to boot a kernel in=20 the zImage format, so the FreeBSD kernel is in a format that modern Xen=20 incorrectly detects as an x86 kernel.

I also watched Julien Grall's 30 minute video presentation of his wo= rk to boot FreeBSD/arm on Xen at FOSDEM 2014 here :

https://archive.fosdem.or= g/2014/schedule/event/freebsd_xen_arm/

In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting=20 occasional crashes and needed to investigate the problem. He mentioned=20 the zImage ABI that Linux uses, but pointed out FreeBSD does not use=20 that format, and back then it was an open question which format to use=20 to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only=20 supported format is still the zImage format that Linux uses.

It looks like Julien's work back then was using an ELF binary to boo= t FreeBSD/arm on Xen instead of the supported zImage format that Linux=20 uses and the modern Xen toolstack exits with an error when trying to=20 boot the FreeBSD ELF formatted binary that Julien's patch creates. So= =20 the best solution would be to try to port the rules to build a FreeBSD=20 kernel in the zImage format instead of the ELF format. I have been=20 studying the Makefiles in Linux to see how Linux builds the Linux arm=20 kernel in the zImage format, but it is not trivial to understand.

=
--
M= ario.
--00000000000057995f060af88d0b-- From nobody Sat Nov 25 12:15:30 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ScrQw4x19z52WGC; Sat, 25 Nov 2023 12:15:36 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ScrQv3s03z4hk1; Sat, 25 Nov 2023 12:15:35 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=P63YzH1s; spf=pass (mx1.freebsd.org: domain of grahamperrin@gmail.com designates 2a00:1450:4864:20::333 as permitted sender) smtp.mailfrom=grahamperrin@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wm1-x333.google.com with SMTP id 5b1f17b1804b1-40b27726369so19538265e9.0; Sat, 25 Nov 2023 04:15:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700914534; x=1701519334; darn=freebsd.org; h=content-transfer-encoding:cc:autocrypt:from:reply-to:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=KL/vpk8T0H8B/mphDeT0BqpMESQvGsv1QO2RRvh5uUg=; b=P63YzH1skZXVpUwUFLdF3MkQRDkhEvRhY+Zx/rYVFeeeXal9Eer01nFpG8pjgXEqH9 OHJ3UlDM6lM9eynFqeV2Bq9bK8NYIbliYa9ZfFtTm8pec8sBQMrdO3/Y8uO7MhY6eDiY 31HvxlQJZWvST/PDUjUs6SKwxUh7K4gZ0dbRxhmQiCPFiyXV9IHINfVyOgwSNazf2cVq UHchDk2rQnWu5D97kh4cchnMG1/5hsPj2TXowSpdbDcrFofM769KoiQYLC913zfW9Nu6 WZQ017kVS57B+u5dMJF7OjuZNMqT1fk+I5khkQbD6tHm0/l4KzarT5u+52eKQVUI5fty ieOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700914534; x=1701519334; h=content-transfer-encoding:cc:autocrypt:from:reply-to:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KL/vpk8T0H8B/mphDeT0BqpMESQvGsv1QO2RRvh5uUg=; b=Ad4W7iH408mKj7Tsh6NNwtkCtu562Sot4aKq7MRJmLNLHhznZyKjKlMhdnjOhOarG5 58bhSFEAQkOQVuWJnhQoEddy2nTPu5//eHm72Q3gUG6Aq2ygkF3CB2nidZhIJwbf+Kr9 VurclIx/Xy5MyifqditEXM8VMylKH7aj62jyli1izHiQ0IzQ7zS3ikci3sRhMXJAnPy0 D4X7isvUq/sY2aCYv8vZZ6CLqg0a+UM0JjGLKZjKvRru1bso5xa/wg6sOv0ngjphlwJG qdGQpKYsqoFauYOhNSF5HNrWAx7HrlhuZw38ks3nbQ5GCtwSZXOqDAO7feGZMc/pOFT4 Jegg== X-Gm-Message-State: AOJu0YwyUy9uOb8uD6wgrQBYrE4FltKibRHUYmhE6195G/ywyDzaDGOf dA/U7uP2FIzmxkbYW73STnVi3A1QxALkzw== X-Google-Smtp-Source: AGHT+IE1nsok3+S8qNkjWvqLd429j4SqPuY4h+rNknxbGMcMnBJR4KS2WiSqrhk9Vp2JeXGtlouMNw== X-Received: by 2002:a05:600c:35d5:b0:401:bcd9:4871 with SMTP id r21-20020a05600c35d500b00401bcd94871mr1002733wmq.21.1700914533649; Sat, 25 Nov 2023 04:15:33 -0800 (PST) Received: from [192.168.1.10] (host-2-100-164-166.as13285.net. [2.100.164.166]) by smtp.gmail.com with ESMTPSA id l6-20020a05600c4f0600b0040b3632e993sm7795287wmq.46.2023.11.25.04.15.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 25 Nov 2023 04:15:33 -0800 (PST) Message-ID: <53ac7e13-bb04-4d6f-bf10-e06d9bb5b909@gmail.com> Date: Sat, 25 Nov 2023 12:15:30 +0000 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Ventoy and FreeBSD Content-Language: en-US To: FreeBSD questions Reply-To: FreeBSD Hackers From: Graham Perrin Autocrypt: addr=grahamperrin@gmail.com; keydata= xsFNBGKYt7ABEAClu83dJ3ZKfVgPOk9YKRv0Z+dl2b88+k9R4vwAmElgguYdKE7yhnQNhhWM v9vi6AFrBMc2oJdVHJ2OrXfwpELBFIgiSMEWNsC4e+Z3HtSajcl+pFZsP7ciiSoycj/w3wIV kAZoVGbhyIbNG7fbCEJ8q81TbfsGypV3bRmbZVvGNecBguYiooBtz2Qht1p3itXMkIA6P9pS YDl+6QddZLyUUAjAnFv2QDoYSHLnaDUWw4oONZsB0SKVu8jMIBh4uJZoYEOvdvc9jQQdOpA2 CAgA6ulfm42Ikr9lKBUUCtjqiWAhJ7iXOTyHAIdR4Mf8alCE6tdTq6dHdIt+GktTY7oYNyL2 3aD3C7I5waU0SFXvJcOMG10QLfwYQMOQoYQ9XJ0U5A28WYiDcylDdUWT7SappP1e1ZMeJWWO y14mxxNzHaJSI4rK8P/p5tp3Q7SSC4k5gMh9zKba3K2ApCWNbVLGvXsJeQkZZNvu70tE81ey AHI5iZcB6D7WaHysBUmsKaEpbcmm1ZThTnGL0SHEl5to5Jab5Fg6O+Cnly5sVz5lX/v8Aosx kKNei7SCVqXOVtteQeGxWbXWbhPgbMyc0Gi3DuxBI/yvJ43k/rJysQlLGLWfJx/UXprwLluC PDK9EvKEB+fD1Z349uzp1sKr3ihpySbyKI8fpudftnAz4EsoCwARAQABzSZHcmFoYW0gUGVy cmluIDxncmFoYW1wZXJyaW5AZ21haWwuY29tPsLBlAQTAQoAPhYhBFk/5bLDBwftvJcvCrdn SG9KGNQLBQJimMMBAhsDBQkFo5qABQsJCAcDBRUKCQgLBRYDAgEAAh4FAheAAAoJELdnSG9K GNQLbHAQAJi998y42bEbq5HmABYovmAEtQj33YSUWyc9QRmAHpN8Er3lTKsgmZcVChB5Fu/d go2oYynDjlVpA7+wiSmg4AG78mOYbg/e19XMhrH0keDKqZXFkU+G7agR0mF09qvpQZ9MTJYZ 2u7FtytZK665UfipOdV8eGn2hFC/WynjUwEzKyryBgbbLAEbfOPeZNry4h2ZPWbtTvx/PE/V X3Vh2oGqYx69DCGz+0xEhy62ZKbkX5SL8LUf/1WViyCVzsHasFxmFxYPWIfBy8ayQ7xapz7M cSXSQyu4oDT4qh9eZiGP9/aAcZKHcV6t9y77JGhUJ/5O1sANKMa3YhgimE+Z86LHYa1IH774 PHj1nAXBwS+Cj/1l/NQoQcyjvOj8zuCsMJVaLMb6B46YsReP4+3yBLpyeBC//t6zWPbgAkWW VjROC0dXUAMTFpnA6NZe3UghG+Nc4fnCLGOhc2nyWFYHIaYV6Hv1ITFSem9DdeNnR1CFm1VM TJ7i7TuqYM+WZTkoUsTf4c46hS/ZNJZSCxh0s9yYr+BYk3XBbd+ElaZ1dJE6cuSVdw15+P2h DnprurxC4byl4YFkn+UAVvQsOgeq6aSHLOHX0weYu1OLoiPYsTdyGhne72+kDhEEdFD5aHdQ PFrbQIrqWLV0a04++0ZwGpNvXtgnWhDdAQJDwGsSSwbLzsFNBGKYt7ABEADRb1tZuh7DPYET 0wK6fe7owbYgM+RfKhmcrGgR2HI9M2q6+0WKF/ITnggWdIW2Ecc4z2boLz/cwvPGCS7/YxZM 61KklGCwuS7q1s04XnHDWHuFxfXQPzAdVmNO3bYoMZbJjHXs6sB2u5ksiwPwaMAWWaGkviSj c5pwvHCiTmX5vH5CBj/Vi+5ESyX38vK4JM5S/m4ouI/6M9biyFgimV+v3vVyCxJCT1gI9g4o GIh1qq5S433b1fihn4yHPf8XOKyBpA/QcwLONViBqJL5nnOxpsh344rNxn2R7CcRzzicOV+e 2IbMem4lwNWQlZKoRotKXZi9LqN5mynSBYqAUdoZum0QinWT9F22B0Qex5PH1zAt9i2W91Vd kcPB3LwkRXj07ycRtsSzpgPA6fLc6AsoWFslHl8kVOO5eJIA4xhjlPa+W8lguQHZ0iX+5uAv 2eAgXR2swADuHPuENNFStmsgAMl8OOOgtq75yA5TpyIzxMuXV9Nmp0VfIaUM/IdLdmxhc1pC c320l5fYMHVLFAReWEbSj2QH8YzWfpXHIegutWWYEbH9SiDXgS9KoKmCJV/Qa+x6/b8y3pOZ vnIbCDaynC2Yr50s8gRa9kb54JE8Z+p8r16U3SEsK3PtUi0RF0e51danCVHrrE6/Hat2XUO/ 6nnYgVgFOrLao6Gh/VMs8wARAQABwsF8BBgBCgAmFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsF AmKYt7ACGwwFCQWjmoAACgkQt2dIb0oY1Av7qg//YjCZg8VXyMzXssgIQpROKKqh5V0UBSQl rM3tq4tWhyg0HVMugQj0Om+iNPsEEOGHkm6tyhHMzlKGpAc/l0iAM+8twIyg44Yo5+DcfFXr OMTbTw9T9jDsWOkOBksxy29iYhgpqpWdDBnhXvrJp/FNAiX8CfzrIOZeFPydDoEiKBEXAxfe a9o5J/JeVnZiUeoiFe7i68nZGsb4JxhPczNfqW12t0Ll5/ibjszg5BgjXiLao0KqbWNh4bS5 CVwH90Or+5qqWgzWPeBiuz+rN2QXE/V/fL44GEj1YKASCqmaiYRgjoRFubz1aq1wCXMXY3Iq d4525rscUgS7HBxbblnyTodUPaamN/2nSzcmE/Pkx8MApDSgZCIhs0RTAg+/AoX4HULV1rSE TQwMrBEQt84Tw5W5rHsvXKr4ZEsJUpbPLWYTISsp23nHR+vZtL/Ug+OWCmHC7X7D21xk/xVJ 4sA1RLJBKdCHtnyA4Unv/kNS1KVGxHnITVyw1a71QJADu4qsdtM5u6CyYUhqhM1oseWtV6j+ Qi8KC/G4C3AgZf06fe2fVl42z2grTabL4bC6FQXMwTX2dsm5NakWjUCmUL8uwsQE7ZA4zKxo EYI1YV9q1birpzncYRupr1qnMoggMUHWq0IBYshFQrEO8PeVUZBw7/GfAeh3argdw2Qu748T Cyw= Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.34 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.98)[-0.978]; NEURAL_SPAM_MEDIUM(0.62)[0.624]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FREEFALL_USER(0.00)[grahamperrin]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_REPLYTO(0.00)[freebsd-hackers@freebsd.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::333:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org,freebsd-hackers@freebsd.org]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4ScrQv3s03z4hk1 X-Spamd-Bar: -- To: FreeBSD questions Cc: FreeBSD Hackers Bcc: the reporter of (14.0-RELEASE dvd1-iso installer used in Ventoy got boot panic) Please be aware of and other discussions, including . Replies to this email should address the freebsd-hackers list alone. Thanks From nobody Sat Nov 25 17:02:43 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ScypQ71f8z51jn6 for ; Sat, 25 Nov 2023 17:02:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ScypQ4dhtz3Fhn for ; Sat, 25 Nov 2023 17:02:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a0bdf4eeb46so58070266b.3 for ; Sat, 25 Nov 2023 09:02:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700931773; x=1701536573; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lJcyYwjFsGDCNUEF2SrPc1fBl800LPaPtK2E4VfkqSk=; b=Em3noFN9pbttYLD3ebSyUU2FmX67+VwjZcNMCmbA+67sOfb4IkdZQINaPY9jAaLvvG CnME70BylLfHioC2TETwbQuCqtJKzQQc5x/W7EuZ1NXwjclKy/dt4Vg0Y5L8DJAj3e2w xeiCNWSOdR0qwRYnz54Z6rEuUNorj/QMXmwNudqsAV5NLwXdz8G0SipvjKTRKONgCAIo tu4CFB4dXTRogK5vNuQBKjA5ZUXO7nS2aBDlvna6q3TmPIS4Tnm5OVZuKNr8UI3mi6Cf SsCuXfcdqL1MgzEcxnGsIDWHDCw/IFE9t8EV7rG1GQS8WXsTBoekDFC7pc6OEzDRq9T3 qwBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700931773; x=1701536573; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lJcyYwjFsGDCNUEF2SrPc1fBl800LPaPtK2E4VfkqSk=; b=buuOBA9jZbfIHlZ8sqjS+ncXDFJNp/ZmOBgWui/vh97UwxYRB2CbR/I4V6wfDMLsyE QFVwOaMuPGUy5M6QwmJDDo8jwv+YXSZGG4Vum80pdbqFWjlgAsHSBA9vKmd7EZH28G5M tFcSuvRl8JiCmG3DTy8XOv+HUdKn1L3hTY0hNFq27CdZBBHl+K27wXcdMHVmix/MEdRt A1kbSqU1y9wikMUOZ42M/llIVCM9tuLeex0FmXJ7sFZxqJ4Sr+loRSfyKMtYvKAmrEpw ksJZlSp4IhmvIKIYCqYUxhKzq1SkIhkhVypWxqn06BrlBvi9Y5kEcIjdF4s7TFJMIhd2 9F0A== X-Gm-Message-State: AOJu0YxmwGt+Szkxmk+K46jQkNMpBtQA7pam8DAgaySPVpUUwaGiAICD mEHNoS5H4418GPPP+U1GJNLEJtElLCsb3r1niVUcoQ== X-Google-Smtp-Source: AGHT+IGt9WzvZLY0tUhXeNt9BnWnm2hSaeduHPjx5ve9C1ZRnPuOtAra26+KL+N3o0hRlFoli27UFdGuH6gX0G+ZPys= X-Received: by 2002:a17:906:693:b0:9fc:9b28:7ff7 with SMTP id u19-20020a170906069300b009fc9b287ff7mr5534824ejb.60.1700931773247; Sat, 25 Nov 2023 09:02:53 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 25 Nov 2023 10:02:43 -0700 Message-ID: Subject: Re: Should we boot the FreeBSD kernel in ELF format or in zImage format ? How? To: Mario Marietto Cc: freebsd-hackers , freebsd-arm@freebsd.org, FreeBSD Current , FreeBSD Mailing List , freebsd-xen@freebsd.org, royger@freebsd.org Content-Type: multipart/alternative; boundary="00000000000021c269060afd0a2c" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4ScypQ4dhtz3Fhn --00000000000021c269060afd0a2c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Marietto wrote: > Hello to everyone. > > we have just virtualized Debian 12 on our arm (32 bit) Chromebook. As hos= t > / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It works > great. But our goal is different. We want to virtualize FreeBSD as domU. > Can we have a working Xen PV network driver for a FreeBSD arm guest ?. I > found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I > would like to know if Julien's work was accepted upstream by FreeBSD, in > which case FreeBSD as a Xen guest on arm should work if we enable the Xen > PV drivers in the FreeBSD on arm kernel. If Julien's work was not accepte= d > upstream by FreeBSD, we will have to find his patches and apply them > ourselves to the FreeBSD on arm kernel. > > We found these slides : > > > https://events.static.linuxfound.org/sites/events/files/slides/Porting%20= FreeBSD%20on%20Xen%20on%20ARM%20.pdf > > Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what w= e > want to find. > > It looks like when that slide presentation was written, there were some > limitations on FreeBSD Xen guests. For example, for our debian bookworm > guest, I am using vcpus =3D '2' to match the number of real cpus on our > Chromebook, but slide 13 mentions support for only 1 VCPU with a FreeBSD > guest, so I will need to change that vcpus =3D '1' in the FreeBSD guest > config unless support for 2 or more vcpus was added later, which is > possible because that slide presentation is 9 years old. > > Here is where I would expect to find the XENHVM FreeBSD on arm kernel > config file: > > https://cgit.freebsd.org/src/tree/sys/arm/conf > > But it is not there unless I am not understanding something correctly. Fo= r > now, unfortunately conclude that the support for Xen on arm that Julien > Grall mentioned in that slide presentation 9 years ago was never added to > the official FreeBSD source code. I am searching the web now to see if th= e > patches that Julien Grall wrote are still posted somewhere online. If we > cannot find them, we can ask here and on the xen-users mailing list. Juli= en > regularly reads that list and responds to question about Xen on arm, so I > think he will tell us how to find the patches if we cannot find them onli= ne. > > According to this page from the FreeBSD wiki: > > https://wiki.freebsd.org/Xen > > I think FreeBSD only supports Xen on x86, not arm. So this is going to be > a bit of a challenge to get a Xen FreeBSD guest on arm working. We know > Julien Grall has some patches that made it work in the past ! > > I found a slightly newer slide presentation by Julien here: > > https://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd > > It is about the same, but it mentions the GENERIC FreeBSD kernel supports > Xen on arm64, but still says we need the XENHVM FreeBSD config for Xen on > arm 32 bit, which I haven't found online yet. > > Please,take a look at this output of the linux kernel that can boot on > Xen, and the FreeBSD kernel that cannot : > > > % file zImage-6.1.59-stb-xen-cbe+ > zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (litt= le-endian) > > % file FREEBSD-XENVIRT > FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), = dynamically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), n= ot stripped > > > The FreeBSD kernel that won't boot is in ELF format but the Linux kernel > that does boot is in zImage format. > > I spent time reading the docs on xenbits.xenproject.org, and according to > those docs Xen on arm only knows how to boot a kernel in the zImage forma= t, > so the FreeBSD kernel is in a format that modern Xen incorrectly detects = as > an x86 kernel. > > I also watched Julien Grall's 30 minute video presentation of his work to > boot FreeBSD/arm on Xen at FOSDEM 2014 here : > > https://archive.fosdem.org/2014/schedule/event/freebsd_xen_arm/ > > In that video, and in other places, Julien mentions that the boot ABI for > FreeBSD/arm on Xen was not yet developed and he was getting occasional > crashes and needed to investigate the problem. He mentioned the zImage AB= I > that Linux uses, but pointed out FreeBSD does not use that format, and ba= ck > then it was an open question which format to use to boot FreeBSD/arm on > Xen. Unfortunately, nine years later, the only supported format is still > the zImage format that Linux uses. > > It looks like Julien's work back then was using an ELF binary to boot > FreeBSD/arm on Xen instead of the supported zImage format that Linux uses > and the modern Xen toolstack exits with an error when trying to boot the > FreeBSD ELF formatted binary that Julien's patch creates. So the best > solution would be to try to port the rules to build a FreeBSD kernel in t= he > zImage format instead of the ELF format. I have been studying the Makefil= es > in Linux to see how Linux builds the Linux arm kernel in the zImage forma= t, > but it is not trivial to understand > Look at kernel.bin in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. It should be easy to adapt the target to build that. I've done similar things with u-boot formats in the past, but that was 4 employers and 20 years ago now. This path is not well trod. I do know that arm64 virtualization with bhyve is hitting the tree. I'm not sure how easy/hard this will be to modernize. I'm interested to see how your explorations go. Warner --00000000000021c269060afd0a2c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Nov 25, 2023 at 4:41=E2=80=AF= AM Mario Marietto <marietto200= 8@gmail.com> wrote:
Hel= lo to everyone.

we have just virtualized Debian 12 on our arm (= 32 bit) Chromebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It=20 works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm=20 guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by= =20 FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we=20 enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's wor= k was not accepted upstream by FreeBSD, we will have to find his patches=20 and apply them ourselves to the FreeBSD on arm kernel.

We found these slides :

https://events.static.linuxfound.org/sites/events/file= s/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf

Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what = we want to find.

It looks like when that slide presentation was written, there were=20 some limitations on FreeBSD Xen guests. For example, for our debian=20 bookworm guest, I am using vcpus =3D '2' to match the number of rea= l cpus=20 on our Chromebook, but slide 13 mentions support for only 1 VCPU with a=20 FreeBSD guest, so I will need to change that vcpus =3D '1' in the F= reeBSD=20 guest config unless support for 2 or more vcpus was added later, which=20 is possible because that slide presentation is 9 years old.

Here is where I would expect to find the XENHVM FreeBSD on arm kernel co= nfig file:

https://cgit.freebsd.org/src/tree/sys/arm/= conf

But it is not there unless I am not understanding something=20 correctly. For now, unfortunately conclude that the support for Xen on=20 arm that Julien Grall mentioned in that slide presentation 9 years ago=20 was never added to the official FreeBSD source code. I am searching the=20 web now to see if the patches that Julien Grall wrote are still posted=20 somewhere online. If we cannot find them, we can ask here and on the=20 xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the=20 patches if we cannot find them online.

According to this page from the FreeBSD wiki:

https://wiki.freebsd.org/Xen

I think FreeBSD only supports Xen on x86, not arm. So this is going=20 to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past !

I found a slightly newer slide presentation by Julien here:

https://www.slide= share.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

It is about the same, but it mentions the GENERIC FreeBSD kernel=20 supports Xen on arm64, but still says we need the XENHVM FreeBSD config=20 for Xen on arm 32 bit, which I haven't found online yet.

Please,take a look at this output of the linux kernel that can boot on X= en, and the FreeBSD kernel that cannot :


% file zImage-6.1.59-stb-xen-cbe+
zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little=
-endian)

% file FREEBSD-XENVIRT         =20
FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dy=
namically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not=
 stripped


The FreeBSD kernel that won't boot is in ELF format but t= he Linux kernel that does boot is in zImage format.

I spent time reading the docs on xenbits.xenproject.org, and=20 according to those docs Xen on arm only knows how to boot a kernel in=20 the zImage format, so the FreeBSD kernel is in a format that modern Xen=20 incorrectly detects as an x86 kernel.

I also watched Julien Grall's 30 minute video presentation of his wo= rk to boot FreeBSD/arm on Xen at FOSDEM 2014 here :

https://archive.fosdem.or= g/2014/schedule/event/freebsd_xen_arm/

In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting=20 occasional crashes and needed to investigate the problem. He mentioned=20 the zImage ABI that Linux uses, but pointed out FreeBSD does not use=20 that format, and back then it was an open question which format to use=20 to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only=20 supported format is still the zImage format that Linux uses.

It looks like Julien's work back then was using an ELF binary to boo= t FreeBSD/arm on Xen instead of the supported zImage format that Linux=20 uses and the modern Xen toolstack exits with an error when trying to=20 boot the FreeBSD ELF formatted binary that Julien's patch creates. So= =20 the best solution would be to try to port the rules to build a FreeBSD=20 kernel in the zImage format instead of the ELF format. I have been=20 studying the Makefiles in Linux to see how Linux builds the Linux arm=20 kernel in the zImage format, but it is not trivial to understand

<= /div>

Look at kernel.bin = in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. It should be e= asy to adapt the target to build that. I've done similar things with u-= boot formats in the past, but that was 4 employers and 20 years ago now.

This path is not well trod. I do know that arm64= virtualization with bhyve is hitting the tree. I'm not sure how easy/h= ard this will be to modernize. I'm interested to see how your explorati= ons go.

Warner
--00000000000021c269060afd0a2c-- From nobody Sat Nov 25 22:20:33 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sd5sh32Cpz528pS; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sd5sh0FJrz3fc5; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a00191363c1so445272766b.0; Sat, 25 Nov 2023 14:21:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700950870; x=1701555670; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=jkrnr40BYs43XvUxtYhA+UdOh6tOUfNhMjLZTZBkmoTgDQG+XGp5JniHEN6Sqefl37 VIZ+LdGQUvf0omiX/o+lHFVeEOwFrqUEQZr1KVdCETfeOcR8Tj2Cce/+ESvuJiG2gpH3 daKP0mlClK4KLAFBF62bT66HAnO7qmGgjSKG7s16c3syIHWLmJsJQyJ3+OEbF+Cce21K HTaZOJr6FNSZZO28IpEmto4LWkUAabtt3Tz+mlJby3SPzJRqPyMrkODjXx+9CvxfG7NI 3Vuvy3vjDPUeM31FuTwh8DaSkXGMVYfQo/hQ9KV8qxJSgPSwbnROB0Y0/bVOW9oiZ5wH T4PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700950870; x=1701555670; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=INwETliex+aPCGivvr38h9lXRAahV/MFa+nLqEVuqCiyI/WPomVY5b8U/6mboKAx06 jrKdeMDVNQpHTx5Su4O2Y4ylFdHcCLqjanfMjHzUMWEX0VQUwRtaO4Haj6J5x2T1q8kg BYrlok0kyP6OjAfcdMnSH0tIpG+hlYS5TPfiVMFYf+muvXa5o1+boWNnzTlLBtEz4CqM EbUIL6Iytnr94zO3FScwgBM8krwPj6PW9SSwkcMsUdUoG0+UVbPHW5ueTJIb6y5G1ggO rqGCHXooLdJA6D7fBCzHHzl/O8Ho5mG0Ob7ei+rctXfLS0lwmzXE71Qjr2yUROHIRY3K c2YA== X-Gm-Message-State: AOJu0YwQBu0HE7pjK1sEKJY81qTvK6+G9QvCiBHkru5/HMpjZHYYju4Q mI2uJC+pc9mVHMJ50IVrgtuUUj9MooAm4kOREFHY7zOyeKY= X-Google-Smtp-Source: AGHT+IEhkzwilMD6ERaL2bwBn3rOcuTDkx1lGUDZ5xkUD+poku47ky/zmkiWI0tfZHohL3AQulxcriuBDhJofy1Va5I= X-Received: by 2002:a17:906:dfcf:b0:a04:937a:f8b0 with SMTP id jt15-20020a170906dfcf00b00a04937af8b0mr5281464ejc.28.1700950869800; Sat, 25 Nov 2023 14:21:09 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 25 Nov 2023 23:20:33 +0100 Message-ID: Subject: Re: Should we boot the FreeBSD kernel in ELF format or in zImage format ? How? To: Warner Losh Cc: freebsd-hackers , freebsd-arm@freebsd.org, FreeBSD Current , FreeBSD Mailing List , freebsd-xen@freebsd.org, royger@freebsd.org Content-Type: multipart/alternative; boundary="0000000000005ff95f060b017cde" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4Sd5sh0FJrz3fc5 --0000000000005ff95f060b017cde Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I really don't know where to start. It sounds too technical for me. I don't even know what to ask to understand where to start. mmm...can someone provide some documentation ? but not too much dense with technicalities. Thanks. On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warner Losh wrote: > > > On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Marietto > wrote: > >> Hello to everyone. >> >> we have just virtualized Debian 12 on our arm (32 bit) Chromebook. As >> host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It >> works great. But our goal is different. We want to virtualize FreeBSD as >> domU. Can we have a working Xen PV network driver for a FreeBSD arm gues= t >> ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on ar= m. >> I would like to know if Julien's work was accepted upstream by FreeBSD, = in >> which case FreeBSD as a Xen guest on arm should work if we enable the Xe= n >> PV drivers in the FreeBSD on arm kernel. If Julien's work was not accept= ed >> upstream by FreeBSD, we will have to find his patches and apply them >> ourselves to the FreeBSD on arm kernel. >> >> We found these slides : >> >> >> https://events.static.linuxfound.org/sites/events/files/slides/Porting%2= 0FreeBSD%20on%20Xen%20on%20ARM%20.pdf >> >> Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what >> we want to find. >> >> It looks like when that slide presentation was written, there were some >> limitations on FreeBSD Xen guests. For example, for our debian bookworm >> guest, I am using vcpus =3D '2' to match the number of real cpus on our >> Chromebook, but slide 13 mentions support for only 1 VCPU with a FreeBSD >> guest, so I will need to change that vcpus =3D '1' in the FreeBSD guest >> config unless support for 2 or more vcpus was added later, which is >> possible because that slide presentation is 9 years old. >> >> Here is where I would expect to find the XENHVM FreeBSD on arm kernel >> config file: >> >> https://cgit.freebsd.org/src/tree/sys/arm/conf >> >> But it is not there unless I am not understanding something correctly. >> For now, unfortunately conclude that the support for Xen on arm that Jul= ien >> Grall mentioned in that slide presentation 9 years ago was never added t= o >> the official FreeBSD source code. I am searching the web now to see if t= he >> patches that Julien Grall wrote are still posted somewhere online. If we >> cannot find them, we can ask here and on the xen-users mailing list. Jul= ien >> regularly reads that list and responds to question about Xen on arm, so = I >> think he will tell us how to find the patches if we cannot find them onl= ine. >> >> According to this page from the FreeBSD wiki: >> >> https://wiki.freebsd.org/Xen >> >> I think FreeBSD only supports Xen on x86, not arm. So this is going to b= e >> a bit of a challenge to get a Xen FreeBSD guest on arm working. We know >> Julien Grall has some patches that made it work in the past ! >> >> I found a slightly newer slide presentation by Julien here: >> >> https://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd >> >> It is about the same, but it mentions the GENERIC FreeBSD kernel support= s >> Xen on arm64, but still says we need the XENHVM FreeBSD config for Xen o= n >> arm 32 bit, which I haven't found online yet. >> >> Please,take a look at this output of the linux kernel that can boot on >> Xen, and the FreeBSD kernel that cannot : >> >> >> % file zImage-6.1.59-stb-xen-cbe+ >> zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (lit= tle-endian) >> >> % file FREEBSD-XENVIRT >> FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),= dynamically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), = not stripped >> >> >> The FreeBSD kernel that won't boot is in ELF format but the Linux kernel >> that does boot is in zImage format. >> >> I spent time reading the docs on xenbits.xenproject.org, and according >> to those docs Xen on arm only knows how to boot a kernel in the zImage >> format, so the FreeBSD kernel is in a format that modern Xen incorrectly >> detects as an x86 kernel. >> >> I also watched Julien Grall's 30 minute video presentation of his work t= o >> boot FreeBSD/arm on Xen at FOSDEM 2014 here : >> >> https://archive.fosdem.org/2014/schedule/event/freebsd_xen_arm/ >> >> In that video, and in other places, Julien mentions that the boot ABI fo= r >> FreeBSD/arm on Xen was not yet developed and he was getting occasional >> crashes and needed to investigate the problem. He mentioned the zImage A= BI >> that Linux uses, but pointed out FreeBSD does not use that format, and b= ack >> then it was an open question which format to use to boot FreeBSD/arm on >> Xen. Unfortunately, nine years later, the only supported format is still >> the zImage format that Linux uses. >> >> It looks like Julien's work back then was using an ELF binary to boot >> FreeBSD/arm on Xen instead of the supported zImage format that Linux use= s >> and the modern Xen toolstack exits with an error when trying to boot the >> FreeBSD ELF formatted binary that Julien's patch creates. So the best >> solution would be to try to port the rules to build a FreeBSD kernel in = the >> zImage format instead of the ELF format. I have been studying the Makefi= les >> in Linux to see how Linux builds the Linux arm kernel in the zImage form= at, >> but it is not trivial to understand >> > > Look at kernel.bin in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. I= t > should be easy to adapt the target to build that. I've done similar thing= s > with u-boot formats in the past, but that was 4 employers and 20 years ag= o > now. > > This path is not well trod. I do know that arm64 virtualization with bhyv= e > is hitting the tree. I'm not sure how easy/hard this will be to modernize= . > I'm interested to see how your explorations go. > > Warner > --=20 Mario. --0000000000005ff95f060b017cde Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I really don't know where to start. It sounds too tech= nical for me. I don't even know what to ask to understand where to star= t. mmm...can someone provide some documentation ? but not too much dense wi= th technicalities. Thanks.

On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warn= er Losh <imp@bsdimp.com> wrote:=


On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Mariet= to <marietto= 2008@gmail.com> wrote:
= Hello to everyone.

we have just virtualized Debian 12 on our ar= m (32 bit) Chromebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It=20 works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm=20 guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by= =20 FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we=20 enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's wor= k was not accepted upstream by FreeBSD, we will have to find his patches=20 and apply them ourselves to the FreeBSD on arm kernel.

We found these slides :

https://events.static.linuxfound.org/sites/events/file= s/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf

Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what = we want to find.

It looks like when that slide presentation was written, there were=20 some limitations on FreeBSD Xen guests. For example, for our debian=20 bookworm guest, I am using vcpus =3D '2' to match the number of rea= l cpus=20 on our Chromebook, but slide 13 mentions support for only 1 VCPU with a=20 FreeBSD guest, so I will need to change that vcpus =3D '1' in the F= reeBSD=20 guest config unless support for 2 or more vcpus was added later, which=20 is possible because that slide presentation is 9 years old.

Here is where I would expect to find the XENHVM FreeBSD on arm kernel co= nfig file:

https://cgit.freebsd.org/src/tree/sys/arm/= conf

But it is not there unless I am not understanding something=20 correctly. For now, unfortunately conclude that the support for Xen on=20 arm that Julien Grall mentioned in that slide presentation 9 years ago=20 was never added to the official FreeBSD source code. I am searching the=20 web now to see if the patches that Julien Grall wrote are still posted=20 somewhere online. If we cannot find them, we can ask here and on the=20 xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the=20 patches if we cannot find them online.

According to this page from the FreeBSD wiki:

https://wiki.freebsd.org/Xen

I think FreeBSD only supports Xen on x86, not arm. So this is going=20 to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past !

I found a slightly newer slide presentation by Julien here:

https://www.slide= share.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

It is about the same, but it mentions the GENERIC FreeBSD kernel=20 supports Xen on arm64, but still says we need the XENHVM FreeBSD config=20 for Xen on arm 32 bit, which I haven't found online yet.

Please,take a look at this output of the linux kernel that can boot on X= en, and the FreeBSD kernel that cannot :


% file zImage-6.1.59-stb-xen-cbe+
zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little=
-endian)

% file FREEBSD-XENVIRT         =20
FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dy=
namically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not=
 stripped


The FreeBSD kernel that won't boot is in ELF format but t= he Linux kernel that does boot is in zImage format.

I spent time reading the docs on xenbits.xenproject.org, and=20 according to those docs Xen on arm only knows how to boot a kernel in=20 the zImage format, so the FreeBSD kernel is in a format that modern Xen=20 incorrectly detects as an x86 kernel.

I also watched Julien Grall's 30 minute video presentation of his wo= rk to boot FreeBSD/arm on Xen at FOSDEM 2014 here :

https://archive.fosdem.or= g/2014/schedule/event/freebsd_xen_arm/

In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting=20 occasional crashes and needed to investigate the problem. He mentioned=20 the zImage ABI that Linux uses, but pointed out FreeBSD does not use=20 that format, and back then it was an open question which format to use=20 to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only=20 supported format is still the zImage format that Linux uses.

It looks like Julien's work back then was using an ELF binary to boo= t FreeBSD/arm on Xen instead of the supported zImage format that Linux=20 uses and the modern Xen toolstack exits with an error when trying to=20 boot the FreeBSD ELF formatted binary that Julien's patch creates. So= =20 the best solution would be to try to port the rules to build a FreeBSD=20 kernel in the zImage format instead of the ELF format. I have been=20 studying the Makefiles in Linux to see how Linux builds the Linux arm=20 kernel in the zImage format, but it is not trivial to understand

<= /div>

Look at kernel.bin = in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. It should be e= asy to adapt the target to build that. I've done similar things with u-= boot formats in the past, but that was 4 employers and 20 years ago now.

This path is not well trod. I do know that arm64= virtualization with bhyve is hitting the tree. I'm not sure how easy/h= ard this will be to modernize. I'm interested to see how your explorati= ons go.

Warner


--
Mario.
--0000000000005ff95f060b017cde--