From nobody Fri Dec 02 03:19:12 2022 X-Original-To: freebsd-arch@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 4NNdTW6vrdz4hyB1 for ; Fri, 2 Dec 2022 03:19:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 4NNdTW2tPxz4Lpv for ; Fri, 2 Dec 2022 03:19:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62b.google.com with SMTP id n20so8809477ejh.0 for ; Thu, 01 Dec 2022 19:19:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YGzhb8kJbMXHu+jDhzGJ9prIsI7aGqG19yQ8qRD5df0=; b=Xq0ekYe0GOGR4m0RH6b6W0LGZqWVQrbUB2+jGbj3fX1Ik3vPr0MbBrpxrnnIO7gu7/ 1iPl8c1zoi55C6LnmB21VhLo+PajdD/Hyxdx8Hg3nYe9JZoobSU42sQGPhrDt4SNaOO+ cBT3YjxttWfQL/7nka2sNNWnskkhoppekniAATYtCLNbRNfpE/xBuPIufc4cscZvYvRG Y3sNeF8engIkivK9bfREBRh6rVGoLCB+bVjNUiLGk7qNTbYD3UqsYUmh1LuVZKHoKBAQ hCzjy8TTUidzNi3U7TC0/N2ZsT+7Qg+PwTIo+5ihf7Y/oAkhiULZS8c3c2odY3+fwV5Z jBuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=YGzhb8kJbMXHu+jDhzGJ9prIsI7aGqG19yQ8qRD5df0=; b=M/F+T2+Bd7mwUxHfhihcDV5LGKkhgyq6rNcbhkVIxlkkTaAbLfLltoSzL05FyFmNjv jtlzUInQDVmKtcFQSsGosXmjcdSIJeXLWKgqQeiJJd2cJCMM9Y1ZG4+tm7DEi5/MWRh+ EottfY0ha6L7yOyOfagu8pIicPrDH/aoO/rppzQ272esLabdwP9SxsYayis5aTQRoYh+ ORnUHHJR/m7o4upTmqQG7CWb9sukQ9GiYfG2Ex1cpy5KGzwPmS7x/R8iF+lW3BuPAzHa aSzyFS3QIZ10QaCJYgIRNKVbJHtj0SMN+H3B+SnL+AT3zb73Plz4bAljt3J77gjHJ6zg /ZfQ== X-Gm-Message-State: ANoB5pmw+WXVWV2MeuOBoRZsx9lJsxLOMvLplwsd1WFRYByo76DsB7GS JOWWkd8a5r+ZUu82EVmMX8u4h241Vpfke4QCFF9Msw== X-Google-Smtp-Source: AA0mqf4Hu7LuzKg+Z0YL15KNuSsSaSlv1G0xxIVbsCpNhbv57gssojPfU5cQ1EHZpt8J3Y15LzaEjW5WGKGegMp1rc0= X-Received: by 2002:a17:906:f24f:b0:7c0:b069:8e5b with SMTP id gy15-20020a170906f24f00b007c0b0698e5bmr4845155ejb.252.1669951165044; Thu, 01 Dec 2022 19:19:25 -0800 (PST) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <9C63C7CB-0416-4F7F-80DB-28C5002A5F36.ref@yahoo.com> <9C63C7CB-0416-4F7F-80DB-28C5002A5F36@yahoo.com> In-Reply-To: <9C63C7CB-0416-4F7F-80DB-28C5002A5F36@yahoo.com> From: Warner Losh Date: Thu, 1 Dec 2022 20:19:12 -0700 Message-ID: Subject: Re: Giant Locked drivers To: Mark Millard Cc: ehem+freebsd@m5p.com, freebsd-arch Content-Type: multipart/alternative; boundary="000000000000fc319c05eecfcddd" X-Rspamd-Queue-Id: 4NNdTW2tPxz4Lpv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[freebsd]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000fc319c05eecfcddd Content-Type: text/plain; charset="UTF-8" On Thu, Dec 1, 2022, 8:13 PM Mark Millard wrote: > Elliott Mitchell wrote on > Date: Fri, 02 Dec 2022 00:33:00 UTC : > > > On Tue, Nov 15, 2022 at 10:37:36AM -0700, Warner Losh wrote: > > > When set to 0, you get today's behavior. If set to 1, it will no longer > > > allow drivers that don't request MPSAFE interrupt handlers from > registering > > > (the interrupt setup will return an error). > > > > > > This will allow us to understand what is lost if we throw the switch, > and > > > allow users to proactively test their systems to see if they are > > > affected or not (and if they are, if they want to live without the > > > functionality, or want to fund work in the area). > > > > > > Comments? > > > > . . . > > > > > > In other news in two handy VMs. On x86: (a full VM with hardware > emulation) > > > > atkbd0: [GIANT-LOCKED] > > psm0: [GIANT-LOCKED] > > WARNING: Device "psm" is Giant locked and may be deleted before FreeBSD > 14.0. > > > > On ARM64: (basically pure VM with no emulated hardware) > > > > > > > > So right now everyone is reporting x86 console devices and nothing else. > > In > https://lists.freebsd.org/archives/freebsd-arch/2022-November/000290.html > I reported that RPi*'s list: > > WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD > 14.0. > > The other two types of small board computers that I have > access to do not have software support for the video. > > I've no evidence beyond those tests to know if the issue is > specific to the RPi*'s vs. more general. > > > This suggests the x86 console is urgent for giant removal. Then perhaps > > it will be viable to default to disabled (or perhaps something else will > > float to the top). > I have the start of patches for newbus. But the console complex is trick since it's one of the few places multiple drivers are all locked by Giant and some care is needed. Warner --000000000000fc319c05eecfcddd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Dec 1, 2022, 8:13 PM Mark Millard <marklmi@yahoo.com> wrote:
Elliott Mitchell <ehem+freebsd_at= _m5p.com> wrote on
Date: Fri, 02 Dec 2022 00:33:00 UTC :

> On Tue, Nov 15, 2022 at 10:37:36AM -0700, Warner Losh wrote:
> > When set to 0, you get today's behavior. If set to 1, it will= no longer
> > allow drivers that don't request MPSAFE interrupt handlers fr= om registering
> > (the interrupt setup will return an error).
> >
> > This will allow us to understand what is lost if we throw the swi= tch, and
> > allow users to proactively test their systems to see if they are<= br> > > affected or not (and if they are, if they want to live without th= e
> > functionality, or want to fund work in the area).
> >
> > Comments?
>
> . . .
>
>
> In other news in two handy VMs. On x86: (a full VM with hardware emula= tion)
>
> atkbd0: [GIANT-LOCKED]
> psm0: [GIANT-LOCKED]
> WARNING: Device "psm" is Giant locked and may be deleted bef= ore FreeBSD 14.0.
>
> On ARM64: (basically pure VM with no emulated hardware)
>
> <nothing>
>
> So right now everyone is reporting x86 console devices and nothing els= e.

In https://lists= .freebsd.org/archives/freebsd-arch/2022-November/000290.html
I reported that RPi*'s list:

WARNING: Device "fb" is Giant locked and may be deleted before Fr= eeBSD 14.0.

The other two types of small board computers that I have
access to do not have software support for the video.

I've no evidence beyond those tests to know if the issue is
specific to the RPi*'s vs. more general.

> This suggests the x86 console is urgent for giant removal. Then perhap= s
> it will be viable to default to disabled (or perhaps something else wi= ll
> float to the top).

<= /div>

I have the start of patc= hes for newbus.

But the = console complex is trick since it's one of the few places multiple driv= ers are all locked by Giant and some care is needed.=C2=A0

Warner=C2=A0
--000000000000fc319c05eecfcddd--