From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4CD79C433ED for ; Fri, 30 Apr 2021 00:20:37 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E40A961107 for ; Fri, 30 Apr 2021 00:20:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E40A961107 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=thesusis.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.120258.227439 (Exim 4.92) (envelope-from ) id 1lcGt8-0003HP-A8; Fri, 30 Apr 2021 00:20:10 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 120258.227439; Fri, 30 Apr 2021 00:20:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1lcGt8-0003HI-7F; Fri, 30 Apr 2021 00:20:10 +0000 Received: by outflank-mailman (input) for mailman id 120258; Fri, 30 Apr 2021 00:20:08 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1lcGt6-0003HD-HL for xen-devel@lists.xenproject.org; Fri, 30 Apr 2021 00:20:08 +0000 Received: from vps.thesusis.net (unknown [34.202.238.73]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 76ac7c02-43e2-4ae8-b860-e1b2d6938946; Fri, 30 Apr 2021 00:20:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vps.thesusis.net (Postfix) with ESMTP id 6E9B22ECD1; Thu, 29 Apr 2021 20:20:07 -0400 (EDT) Received: from vps.thesusis.net ([127.0.0.1]) by localhost (vps.thesusis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oj1xF6OGsgDn; Thu, 29 Apr 2021 20:20:07 -0400 (EDT) Received: by vps.thesusis.net (Postfix, from userid 1000) id 3B0DE2ECD0; Thu, 29 Apr 2021 20:20:07 -0400 (EDT) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 76ac7c02-43e2-4ae8-b860-e1b2d6938946 References: <87o8dw52jc.fsf@vps.thesusis.net> <87fsz84zn1.fsf@vps.thesusis.net> User-agent: mu4e 1.5.7; emacs 26.3 From: Phillip Susi To: Dmitry Torokhov Cc: xen-devel@lists.xenproject.org, linux-input@vger.kernel.org Subject: Re: Xen Virtual Keyboard modalias breaking uevents Date: Thu, 29 Apr 2021 20:11:03 -0400 In-reply-to: Message-ID: <87o8dw8vyg.fsf@vps.thesusis.net> MIME-Version: 1.0 Content-Type: text/plain Dmitry Torokhov writes: > Not every keyboard, but all keycodes above KEY_MIN_INTERESTING which is > KEY_MUTE, so that interested handlers could match on devices they are > interested in without first opening them or poking through sysfs. /Shouldn't/ they be reading sysfs attributes to find that information out though? Isn't modalias there to help modprobe find the right module that wants to bind to this device, which doesn't happen for input devices? If user space is looking at this information then isn't it getting it by reading from sysfs anyway? What in user space looks at input devices other than X and Wayland? And those aren't looking for particular "interesting" keys are they? > I don't know why Xen keyboard exports that many keycodes ;) In general, > my recommendation is to mirror the physical device when possible, and > instantiate several devices so there is 1:1 relationship between virtual > and physical devices. Xen guys: any input as to why it supports so many "interesting" keys?