Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp1744653iob; Thu, 19 May 2022 13:27:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwTHWQWDf+GJZiwYxy75SXheF7bHxuuOTkEvgFMtleuZJis0dVcABCGRGEHMN5HMukBrmVr X-Received: by 2002:a17:902:cecb:b0:161:bbbf:c45f with SMTP id d11-20020a170902cecb00b00161bbbfc45fmr6337968plg.155.1652992037869; Thu, 19 May 2022 13:27:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652992037; cv=none; d=google.com; s=arc-20160816; b=xhGxmYAEUcVnJszZfqSJG3f2OQLtYm8MdN4IlJnISAZWPlamyKhpGdxWbfvu+zufc6 zWoXRkpPqRrvGM1ZdneuoE1To7tETXgTJHvTYg/ZGSrHYfWO8Hus25UQBZPysbrcQ+iT BiKGtVDRyyHXzU+3bRMFH5j/iQnctVN513s5JaD4aIPtonpHRg9DK1Z4RZyTEu6xOTHZ +Vxq1SQYS32kB/e5SpXePjsT5dsB3LKUqGAga9YnMf/9uUT/Aa+wLCabpkp6Ltsn4UHp 0wZAyw/0gK4z5HZyGJO0WTjmC+de0ZQVaBXMpW46USUw9Rj76JE4IzwTdqj0ialFoyp2 9pTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=TH+ICKBkv+npEh8DphvHokm9BJGopIGyRclr3HlZVLs=; b=o4WVbMYNxcGhtOgCDiSnnFkNTNZ8VFIqZ/E6zYi9acxC2RTdfFOR8PuWgGfQ6ITvdz DFxaTKDY4JSxgOVEPGK5uaeTi1P+zxNyNFBwSpTFFQbacg+JIYTpm8ADlR80fqqLBj22 pzwtVoXi3ZzM+ud3wrJcwgPrUPeqS3XOtZ++SqDs6GEX95e6pTtGnQjK/RUOeVMhWwRU QLzDy2ZaxeUrzKc1uODi+txbT3BmnrMloZEEhpkbFElYcMifcFyDxrtGa807AuDIpyuM A95aG9D/PM588UbqvuY7JQZ7eirN+SRvUm4YDev+fo/i+0FiRHtoEq6KurEFQJiMQ/jA 4jJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="T3/WxuLk"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i2-20020a654d02000000b003f5f7c02535si8188708pgt.38.2022.05.19.13.27.04; Thu, 19 May 2022 13:27:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="T3/WxuLk"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236921AbiESKnY (ORCPT + 99 others); Thu, 19 May 2022 06:43:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45610 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230011AbiESKnW (ORCPT ); Thu, 19 May 2022 06:43:22 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 9B814AEE21 for ; Thu, 19 May 2022 03:43:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652956996; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TH+ICKBkv+npEh8DphvHokm9BJGopIGyRclr3HlZVLs=; b=T3/WxuLkJCrVB9de5Uj6J5y573YR5VZ0mutWbBv5/HurfaesQMqhD4aBP0sB35v/Qinnwu 13CTVjllWhAmqtHQAJiYX2XFy2iwk+okvytRdnDtWRCw4QS3L8pwDIP/Ij4NIRMEoRIPYX uzftSNWjwub08gr8u6odOcyMq0yPRQ4= Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-445-t5z-ndYgNGmn0IK7nIrOPA-1; Thu, 19 May 2022 06:43:15 -0400 X-MC-Unique: t5z-ndYgNGmn0IK7nIrOPA-1 Received: by mail-ej1-f70.google.com with SMTP id gn26-20020a1709070d1a00b006f453043956so2320167ejc.15 for ; Thu, 19 May 2022 03:43:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=TH+ICKBkv+npEh8DphvHokm9BJGopIGyRclr3HlZVLs=; b=NxlH4VVclaeNaNHT+ICxmwrSyq3fYyJgJNY2ls2zko4DjKw4iDKTB8IoRT2kMT67H+ 7lmpt7hk6syclTMtNxC732Uj65Zifs79dAYdt7UE8fVmkJqH0KXgs51w/fpEFZPJ+1jO nfwtpHviRuJIfKTpsR9m6acGiCAH/0JRtNsN+CTYfc23hO09BiMv2+7Vs5nVRzfMHuZb i2wXQ9wwnc3W501mZt5qFWvFvxT+TbfAT9q0xpAbxu39tJFWQJWUPx5fOREuFyyk86cA OqURBbx9LXK/JnYhh1PEEmotaF37YER2/ahaoQvS3qxjLYx7/aOIcBiPgs2vOw/xp+Ou QVTQ== X-Gm-Message-State: AOAM531/Tngxn8g90YPBGSUgW56+BkIHFzHxu7VjyXKS09jxmsf6gFC7 q1T0oGDr2lKCI+lbsi1xuuuDybhEeai0whwqsSLXCG8jzN5SgzdLo8/a1VOhZS8O/CEM7bAfAWQ +Fk26T12XQA7854gyKkr2dm2i X-Received: by 2002:a17:907:7248:b0:6fe:a121:d060 with SMTP id ds8-20020a170907724800b006fea121d060mr219602ejc.9.1652956994172; Thu, 19 May 2022 03:43:14 -0700 (PDT) X-Received: by 2002:a17:907:7248:b0:6fe:a121:d060 with SMTP id ds8-20020a170907724800b006fea121d060mr219560ejc.9.1652956993791; Thu, 19 May 2022 03:43:13 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id d12-20020a056402000c00b0042617ba637bsm2571532edu.5.2022.05.19.03.43.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 May 2022 03:43:13 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id A871E38EE12; Thu, 19 May 2022 12:43:12 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Benjamin Tissoires , Christoph Hellwig Cc: Greg KH , Jiri Kosina , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Shuah Khan , Dave Marchevsky , Joe Stringer , Jonathan Corbet , Tero Kristo , lkml , "open list:HID CORE LAYER" , Networking , bpf , "open list:KERNEL SELFTEST FRAMEWORK" , Linux Doc Mailing List Subject: Re: [PATCH bpf-next v5 00/17] Introduce eBPF support for HID devices In-Reply-To: References: <20220518205924.399291-1-benjamin.tissoires@redhat.com> X-Clacks-Overhead: GNU Terry Pratchett Date: Thu, 19 May 2022 12:43:12 +0200 Message-ID: <87ee0p951b.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Benjamin Tissoires writes: > On Thu, May 19, 2022 at 10:39 AM Christoph Hellwig wrote: >> >> On Thu, May 19, 2022 at 10:20:35AM +0200, Greg KH wrote: >> > > are written using a hip new VM? >> > >> > Ugh, don't mention UDI, that's a bad flashback... >> >> But that is very much what we are doing here. >> >> > I thought the goal here was to move a lot of the quirk handling and >> > "fixup the broken HID decriptors in this device" out of kernel .c code >> > and into BPF code instead, which this patchset would allow. > > Yes, quirks are a big motivation for this work. Right now half of the > HID drivers are less than 100 lines of code, and are just trivial > fixes (one byte in the report descriptor, one key mapping, etc...). > Using eBPF for those would simplify the process from the user point of > view: you drop a "firmware fix" as an eBPF program in your system and > you can continue working on your existing kernel. How do you envision those BPF programs living, and how would they be distributed? (In-tree / out of tree?) -Toke