Received: by 2002:a05:6520:4211:b029:f4:110d:56bc with SMTP id o17csp1552100lkv; Wed, 19 May 2021 12:35:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxWv5SkHiOFjL9k8FStreB9LKsB/JuXlLqdl8/HXsVFAxh2VT6tJ1PX1tRHIvYRkCjHFB+a X-Received: by 2002:a05:6402:40c:: with SMTP id q12mr723617edv.0.1621452942749; Wed, 19 May 2021 12:35:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621452942; cv=none; d=google.com; s=arc-20160816; b=F5zYSL09kH342aIEOuSlwAA59RxeEcaDR2jZ5uCrZa0+cmIjCphyPYzEYqjVcTjRzq 4S5YFDqSCz/VU4X4r7CWbSenXxSaQ7dqiRLbLG+03MDqfLeHonR0z1AuC+wq+h8wlZ6f 0K4HPzoU6tEB34+RxM8LcthSGdi5kNmC+Xzju+2HNbM5xWR3IR0oZiqVu03Ne7+ydexK 3wyWZcqvQ12jzN3a6kE4QmxzN8FvyOuw9WMF+R0pifSVzmFMBB6lrSIYIfsIOXszmQcL Y/sZ3U+uAur/AANh3F7Hx2JK+jlvT8tYzUoOx3QrZMgQi1SltSlZX2haZa9bqbFWUH2V rQCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject:from :references:cc:to:dkim-signature; bh=Utix8t6spaKb207Zj7UyYQmhE/BXGv3+F72MAkz+g6c=; b=IU0lFR46zV/mUd9UZX8Ly65P9u3NH5TXatMrZR4nFOKNc+yieTrrSSx/sIF8RGM4hg EtbQVvubtnRuAPtrGy1EN1L9CWbG1K/I2xb2vY3bhcHM3tq03QyeIkg+ormbDt+/uh3N 6FXAPDy11vVsCfEj93demS16YkXOhy/6wzVpouZihx7iC95KBxuqh1tWg/JvQ73aMy9V oKA02XumY3Vj8WfP28X5PMIXAJhrL/hArVIjbSIQOvkg/oYC0YX+1RECLx6QuoqfnKTa Pfy9YNLfK45XlhMRtsJhnUCTC0fCdhZwPg5l/s41YJLqZUmaFXl6R2Pd7bVtO/lLGdPF 6ZgQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Ky/yzhgs"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w15si86728edr.379.2021.05.19.12.35.15; Wed, 19 May 2021 12:35:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="Ky/yzhgs"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1353708AbhESNax (ORCPT + 99 others); Wed, 19 May 2021 09:30:53 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:31520 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1353701AbhESNaw (ORCPT ); Wed, 19 May 2021 09:30:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1621430972; 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=Ky/yzhgso1H+eOGamHupsO5oIuOp5PkM73OZARHbhAet5XUt5m5SS7NgXF/9neC/4f/SOO nXXRL/h7JXwzsGeKFMzYC52lbbegXxZtoI5VcZ0naXdfi4MeevtzyCSaVZGmDEyIthKukW MKqugPI9SXNsHeZIskXrwz2HPcI8VVg= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-367-EStJBb3yPguKkAg-CcoVog-1; Wed, 19 May 2021 09:29:28 -0400 X-MC-Unique: EStJBb3yPguKkAg-CcoVog-1 Received: by mail-wr1-f72.google.com with SMTP id h104-20020adf90710000b029010de8455a3aso7153352wrh.12 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=ltDhVoy6xru85yjm4cHkZOAXcI+8px3OLwFYPfHZM/6b8pu4JjwpZpobJ3mhiOZmBX 6uFqzRQ4+5/tTQ1ELvPKqTBjutwpGw/kh5GpvaUleyRnrd1uGLx5E7viUCVScf9Z9fpX 1+uZn4P45962HDLHWP/eQmYl9BIdPa+7ZasIfoID3gqXHBNR7IRTn44y1T/TPcbc0DAQ uVF0Ik4hYVg4BdK39oprGx8d+3+oiIeK28nONOypcwaTwXPRqjdt/g0XTsxLkx/ou/IA FpVWsZwRSEJzCMdsjL3P5KUmJpFL8tai2CqJdK/ZUtVb0W97OTx8ceRxfaCltZLQaCOm TDIg== X-Gm-Message-State: AOAM532N9D9OWY2hnCavpWWYE45muVnZTdMZYMQXMUVPUKxvGRH4uZNh 6iiQxOaR4joclFLEyFgNQGl13JQfacsC209IzmPsIRY/9nTD2v0Yw4uy/zX90xutHPgZHPDyt0v iLRfme9RJ1RtNrNIYl7SWDPKK X-Received: by 2002:a5d:4946:: with SMTP id r6mr7406504wrs.123.1621430967435; Wed, 19 May 2021 06:29:27 -0700 (PDT) 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 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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