From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A24E772 for ; Wed, 19 May 2021 13:29:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621430970; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Utix8t6spaKb207Zj7UyYQmhE/BXGv3+F72MAkz+g6c=; b=Qbb/mwizV9bWxruzNoPEugP3A1X7PLyy2B8LS36wSX2H0Tf/deSNFjCYg325zGj8guNsD+ fvZrryMkM6LmF5BPcH+kikiLCvXxKqTPhKip+I2e5DCtTXZBG3OfjPvH0ggizG9QDRiOZd LLfy4A/kDuqFyERmQYUlD66CVB0GDHg= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-550-Tom_rxDENByEvez7VOwkkg-1; Wed, 19 May 2021 09:29:29 -0400 X-MC-Unique: Tom_rxDENByEvez7VOwkkg-1 Received: by mail-wm1-f71.google.com with SMTP id b128-20020a1c1b860000b029015b52bdb65aso1532926wmb.5 for ; Wed, 19 May 2021 06:29:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:references:from:subject:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Utix8t6spaKb207Zj7UyYQmhE/BXGv3+F72MAkz+g6c=; b=UAyh6zGJhTy75vcRNVuJlSrZRbHqxOqWe8pgJ8Kjr7A35z4TS2RqR9It/xDCQ3xxhF bglHmicStX2o0jWpPwByke6qdwYElWX8MBFD7bwU1HFDklBMF7g4X071CmWeBxsvV59z zb6aX8lNMovYAxzlSZ1b2lHlcDoqhm2qgz9ElixpbdOG1lAubcI5kQHjUROlpfEIS5GT x2k4w0/R88YJ39ujVi35nZHRGnmXFERq6L43f7pP+9P00XHRWNbDmi1dkxWoUjPSBtGo T6nr8mW64lqWwrqwaw+xJXfdj/VCIeQjickM6Yo4dgJap7DB7qHHJnkorLbLIjtRVFEj 06eg== X-Gm-Message-State: AOAM533BvVCr6mn96qR6n1u/6XGTUmCmEYwBEsQlVXN38b7C9DJiB97j pG2CGJO66P/caBw5CRhedlyMg6LLDwlVPLICFQ8GUC+jbkqJRVq1AxRK+lB7alQ42mY3+5YpPR9 AHgCy6kD9oH0yOAF+F4nx+ivkpWag488qj40Z8SqComds1Zrjm/udLDoE42A4VoMyEHWD6ux/aV 4zWA== X-Received: by 2002:a5d:4946:: with SMTP id r6mr7406523wrs.123.1621430967527; Wed, 19 May 2021 06:29:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5mZQHnE/EnIv4pnudlM+/lE7mYzi7oQJa6EidXFKUYAuQiAiWM9tIETxbilaUxzeh7C/zPA== X-Received: by 2002:a5d:4946:: with SMTP id r6mr7406476wrs.123.1621430967215; Wed, 19 May 2021 06:29:27 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:c8dd:75d4:99ab:290a? ([2001:b07:6468:f312:c8dd:75d4:99ab:290a]) by smtp.gmail.com with ESMTPSA id l18sm25469067wrt.97.2021.05.19.06.29.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 May 2021 06:29:26 -0700 (PDT) To: Greg Kroah-Hartman Cc: Anup Patel , Anup Patel , Palmer Dabbelt , Palmer Dabbelt , Paul Walmsley , Albert Ou , Jonathan Corbet , Alexander Graf , Atish Patra , Alistair Francis , Damien Le Moal , KVM General , kvm-riscv@lists.infradead.org, linux-riscv , linux-doc@vger.kernel.org, "linux-kernel@vger.kernel.org List" , linux-staging@lists.linux.dev References: <20210519033553.1110536-1-anup.patel@wdc.com> From: Paolo Bonzini Subject: Re: [PATCH v18 00/18] KVM RISC-V Support Message-ID: Date: Wed, 19 May 2021 15:29:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=pbonzini@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit On 19/05/21 14:23, Greg Kroah-Hartman wrote: >> - the code could be removed if there's no progress on either changing the >> RISC-V acceptance policy or ratifying the spec > > I really do not understand the issue here, why can this just not be > merged normally? Because the RISC-V people only want to merge code for "frozen" or "ratified" processor extensions, and the RISC-V foundation is dragging their feet in ratifying the hypervisor extension. It's totally a self-inflicted pain on part of the RISC-V maintainers; see Documentation/riscv/patch-acceptance.rst: We'll only accept patches for new modules or extensions if the specifications for those modules or extensions are listed as being "Frozen" or "Ratified" by the RISC-V Foundation. (Developers may, of course, maintain their own Linux kernel trees that contain code for any draft extensions that they wish.) (Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/riscv/patch-acceptance.rst) > All staging drivers need a TODO list that shows what needs to be done in > order to get it out of staging. All I can tell so far is that the riscv > maintainers do not want to take this for "unknown reasons" so let's dump > it over here for now where we don't have to see it. > > And that's not good for developers or users, so perhaps the riscv rules > are not very good? I agree wholeheartedly. I have heard contrasting opinions on conflict of interest where the employers of the maintainers benefit from slowing down the integration of code in Linus's tree. I find these allegations believable, but even if that weren't the case, the policy is (to put it kindly) showing its limits. >> Of course there should have been a TODO file explaining the situation. But >> if you think this is not the right place, I totally understand; if my >> opinion had any weight in this, I would just place it in arch/riscv/kvm. >> >> The RISC-V acceptance policy as is just doesn't work, and the fact that >> people are trying to work around it is proving it. There are many ways to >> improve it: > > What is this magical acceptance policy that is preventing working code > from being merged? And why is it suddenly the rest of the kernel > developer's problems because of this? It is my problem because I am trying to help Anup merging some perfectly good KVM code; when a new KVM port comes up, I coordinate merging the first arch/*/kvm bits with the arch/ maintainers and from that point on that directory becomes "mine" (or my submaintainers'). Paolo