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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 66328C433F5 for ; Thu, 4 Nov 2021 16:41:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3ED6B61213 for ; Thu, 4 Nov 2021 16:41:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231587AbhKDQnm (ORCPT ); Thu, 4 Nov 2021 12:43:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45510 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230420AbhKDQnl (ORCPT ); Thu, 4 Nov 2021 12:43:41 -0400 Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B5273C061714 for ; Thu, 4 Nov 2021 09:41:03 -0700 (PDT) Received: by mail-io1-xd33.google.com with SMTP id d70so6664433iof.7 for ; Thu, 04 Nov 2021 09:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=KNVu5VlvLHC8LhEZJ1GeRcJxuhRBVKjlxW5S2JjtSy5YETOQgBq1h80cs+LZg6Jrqq 66dkdvi1vERwy7tSwNjJJVnGC2YPONc/uMbJ8F9Wt//VhGN6Bgfy8P2/BCYZxXwZk3R1 7jjndXad3DE+ZzFuwchi2YDL6NCF1UmgjvK3EPTDCGF0KzmaGIJ/cw9u2JnrLEGcIgDg cihXdT1LQ2nQkR3V/olZ2iTMpBSX9YF6CSg3qCUxleBhwC0c3O7A8Lxw++Oo16bEWP0T uWk4JRKXYmVcJKvDWra+KeLtBtGZVMafA4/kDPlmmu698FI0WE5rTmE9w86bcHEGsQeS mO2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=QpUZCliC/KBaJn9pHwUAPT46E4QYIqWX8/RpMmrSZrwDvrMlOe6WLvpwBSOXt+HH0V nynkEN4W52V9v+R7p4R8Zb0jM7rZkW0FaOvhrg/pyEz0If8qv/P+r/6LMXnyTjTncMud Io8ktO1xPWILCtrYLjkEnLuAROwzL3VyPnsWYzitNFa7536UKEWd6PREFQA/LtmjW0Qf gZ68qdpU0sc6hO5WlZMy7HuJ77dU+ahZaWR8xaotZ+alBKh9NpaYctq1as9k/6EzQk2U aTnaUM6ts8xbHB0ISpMBVQWGh7Z1uqr+0hDUGPx6Huzp3TdMHK/7OD3h7liLjpO8yVrM IZFg== X-Gm-Message-State: AOAM533S7AdGxlkNARTVPIXEuTCvxL3cUq3bEXMmemFToGxU/yOPjXFp D39/iPZQx+c7g0UYiTKbpsKceQ== X-Google-Smtp-Source: ABdhPJzhfKc56+AGehB6rwlydFBdwcHeviUbHIFnDTRU6KIyTbtZIkuuDhw1XuIj5pRTYfxo6B4M8Q== X-Received: by 2002:a5e:8c05:: with SMTP id n5mr6480970ioj.0.1636044062919; Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Received: from google.com (194.225.68.34.bc.googleusercontent.com. [34.68.225.194]) by smtp.gmail.com with ESMTPSA id u12sm1074124iop.52.2021.11.04.09.41.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Date: Thu, 4 Nov 2021 16:40:58 +0000 From: Oliver Upton To: Reiji Watanabe Cc: Marc Zyngier , kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, James Morse , Alexandru Elisei , Suzuki K Poulose , Paolo Bonzini , Will Deacon , Andrew Jones , Peng Liang , Peter Shier , Ricardo Koller , Jing Zhang , Raghavendra Rao Anata Subject: Re: [RFC PATCH v2 18/28] KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability Message-ID: References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-19-reijiw@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211103062520.1445832-19-reijiw@google.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, Nov 02, 2021 at 11:25:10PM -0700, Reiji Watanabe wrote: > Introduce a new capability KVM_CAP_ARM_ID_REG_WRITABLE to indicate > that ID registers are writable by userspace. > > Signed-off-by: Reiji Watanabe > --- > Documentation/virt/kvm/api.rst | 8 ++++++++ > arch/arm64/kvm/arm.c | 1 + > include/uapi/linux/kvm.h | 1 + > 3 files changed, 10 insertions(+) > > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst > index a6729c8cf063..f7dfb5127310 100644 > --- a/Documentation/virt/kvm/api.rst > +++ b/Documentation/virt/kvm/api.rst > @@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset > of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace > the hypercalls whose corresponding bit is in the argument, and return > ENOSYS for the others. > + > +8.35 KVM_CAP_ARM_ID_REG_WRITABLE > +-------------------------------- ID registers are technically already writable, KVM just rejects any value other than what it derives from sanitising the host ID registers. I agree that the nuance being added warrants a KVM_CAP, as it informs userspace it can deliberately configure ID registers with a more limited value than what KVM returns. KVM_CAP_ARM_ID_REG_CONFIGURABLE maybe? Naming is hard :) -- Thanks, Oliver 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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1B2FC433EF for ; Thu, 4 Nov 2021 16:41:08 +0000 (UTC) Received: from mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by mail.kernel.org (Postfix) with ESMTP id 3C60961213 for ; Thu, 4 Nov 2021 16:41:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 3C60961213 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.cs.columbia.edu Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id BB91140642; Thu, 4 Nov 2021 12:41:07 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Authentication-Results: mm01.cs.columbia.edu (amavisd-new); dkim=softfail (fail, message has been altered) header.i=@google.com Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqQT71FHMDiZ; Thu, 4 Nov 2021 12:41:05 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id D44BD4A19F; Thu, 4 Nov 2021 12:41:05 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id F283B406E7 for ; Thu, 4 Nov 2021 12:41:04 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eD9gbf3gJujt for ; Thu, 4 Nov 2021 12:41:03 -0400 (EDT) Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id B1F6840642 for ; Thu, 4 Nov 2021 12:41:03 -0400 (EDT) Received: by mail-io1-f41.google.com with SMTP id v65so7622194ioe.5 for ; Thu, 04 Nov 2021 09:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=KNVu5VlvLHC8LhEZJ1GeRcJxuhRBVKjlxW5S2JjtSy5YETOQgBq1h80cs+LZg6Jrqq 66dkdvi1vERwy7tSwNjJJVnGC2YPONc/uMbJ8F9Wt//VhGN6Bgfy8P2/BCYZxXwZk3R1 7jjndXad3DE+ZzFuwchi2YDL6NCF1UmgjvK3EPTDCGF0KzmaGIJ/cw9u2JnrLEGcIgDg cihXdT1LQ2nQkR3V/olZ2iTMpBSX9YF6CSg3qCUxleBhwC0c3O7A8Lxw++Oo16bEWP0T uWk4JRKXYmVcJKvDWra+KeLtBtGZVMafA4/kDPlmmu698FI0WE5rTmE9w86bcHEGsQeS mO2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=J0Bz/+jCkuPjdjXDcHgDCRhX/Zluaq45YydHWbcgZ22U1QhPX56sq/DxAR/uCR0AhG z6HxWCf+rLs2y/Z2PHI+pfsgB+gCD4oCs9jU9PDNfs+RFl944dzrj8CPcWp5QJZIvPDg w6NCU+qvGAR9V3/GNXwy4kVG4B/+EPfB8lMKc1YfsJvQ/MVAXBJ5nW/DUj9hvEkkHY/J cZzwRtLqgHjtzsrbdEcoET2QOJht+PTczePSeR7aN3PF+xYc450n3EAOfpjal/Vin0U1 Tzwj09K8UmfNaC6m0K0r168IYTHGvrxulpl/LZGqFzSsI+lO1FI15j4Tzz+ckb4ELP8l m+YA== X-Gm-Message-State: AOAM532i6Ymk/JrLnj4xm6sXmKALTr+yMTCLiuao3+cZawmI4fN6m+tO F657FSgIUrbwJfIzZhgede81JA== X-Google-Smtp-Source: ABdhPJzhfKc56+AGehB6rwlydFBdwcHeviUbHIFnDTRU6KIyTbtZIkuuDhw1XuIj5pRTYfxo6B4M8Q== X-Received: by 2002:a5e:8c05:: with SMTP id n5mr6480970ioj.0.1636044062919; Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Received: from google.com (194.225.68.34.bc.googleusercontent.com. [34.68.225.194]) by smtp.gmail.com with ESMTPSA id u12sm1074124iop.52.2021.11.04.09.41.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Date: Thu, 4 Nov 2021 16:40:58 +0000 From: Oliver Upton To: Reiji Watanabe Subject: Re: [RFC PATCH v2 18/28] KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability Message-ID: References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-19-reijiw@google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20211103062520.1445832-19-reijiw@google.com> Cc: kvm@vger.kernel.org, Marc Zyngier , Peter Shier , Will Deacon , Paolo Bonzini , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Tue, Nov 02, 2021 at 11:25:10PM -0700, Reiji Watanabe wrote: > Introduce a new capability KVM_CAP_ARM_ID_REG_WRITABLE to indicate > that ID registers are writable by userspace. > > Signed-off-by: Reiji Watanabe > --- > Documentation/virt/kvm/api.rst | 8 ++++++++ > arch/arm64/kvm/arm.c | 1 + > include/uapi/linux/kvm.h | 1 + > 3 files changed, 10 insertions(+) > > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst > index a6729c8cf063..f7dfb5127310 100644 > --- a/Documentation/virt/kvm/api.rst > +++ b/Documentation/virt/kvm/api.rst > @@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset > of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace > the hypercalls whose corresponding bit is in the argument, and return > ENOSYS for the others. > + > +8.35 KVM_CAP_ARM_ID_REG_WRITABLE > +-------------------------------- ID registers are technically already writable, KVM just rejects any value other than what it derives from sanitising the host ID registers. I agree that the nuance being added warrants a KVM_CAP, as it informs userspace it can deliberately configure ID registers with a more limited value than what KVM returns. KVM_CAP_ARM_ID_REG_CONFIGURABLE maybe? Naming is hard :) -- Thanks, Oliver _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm 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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A92F6C433F5 for ; Thu, 4 Nov 2021 16:42:23 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 6E69E61213 for ; Thu, 4 Nov 2021 16:42:23 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 6E69E61213 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=5zCJuR9RhbbxyhXjr2dg2/+BUA80q6+BX9mxUyYEdTM=; b=UkKisQPoD4VPQI JyDBlWuV2Xcgx9Gm3ylWH4z7FCGCwwUBHP5VkxpIg2cBvynz6d2XNWKtQ5zeCez23R0wHnWbQQ9PU Y4pdNLd2pzjAxCmVT++QJZK//DmFAiiK4tXJpxQ0XodqkzacsKhbmu1oUqU97Zir9KeWpeGoQ/JWQ QS95pEsrED8bQaqqNHgAZf+USyjVIiW8kqRQeSH9a3nRRSnde1aIwNTy0ea/MHdMJPX/S28am/Rm4 z+jSr+lCGsvJKRb3Loqo1QSTRTDZPUFZ55Uk3QWe3+rFSmQoTT73+1szkC0AdBCqXzfAQo9D/j/fr EFhjXx77qxk/oT7juPUA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mifnX-009VkS-9p; Thu, 04 Nov 2021 16:41:07 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mifnT-009Vjr-Qz for linux-arm-kernel@lists.infradead.org; Thu, 04 Nov 2021 16:41:05 +0000 Received: by mail-io1-xd33.google.com with SMTP id f9so7520077ioo.11 for ; Thu, 04 Nov 2021 09:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=KNVu5VlvLHC8LhEZJ1GeRcJxuhRBVKjlxW5S2JjtSy5YETOQgBq1h80cs+LZg6Jrqq 66dkdvi1vERwy7tSwNjJJVnGC2YPONc/uMbJ8F9Wt//VhGN6Bgfy8P2/BCYZxXwZk3R1 7jjndXad3DE+ZzFuwchi2YDL6NCF1UmgjvK3EPTDCGF0KzmaGIJ/cw9u2JnrLEGcIgDg cihXdT1LQ2nQkR3V/olZ2iTMpBSX9YF6CSg3qCUxleBhwC0c3O7A8Lxw++Oo16bEWP0T uWk4JRKXYmVcJKvDWra+KeLtBtGZVMafA4/kDPlmmu698FI0WE5rTmE9w86bcHEGsQeS mO2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=n89uubugbDSS31fmjZBPGlZmDbloGpPz8qHQD795FjI=; b=n/yrkFgJ6SL2O5WVIb6/OoG9jz4roROJmxPpwG9yuypVdx8jgf6G3G7vLHjRtkMiJE xJxrm6mQv9/LMWy+tfdAQByjh+jrbzS5To09/SApjCw+gBpRj0OgKaelm/IX8oPjM95C JqA4ZAp9yaB0vZYIQOJMzhzZWs7PjUhHfDJbEsauzzTfkPpI+hjNvqCoIiUYjwaBXZjd cvbO4jlt4CsiqGr2WpUdw45Ffkjwi5J7jt3OwM1bXZY8thvdDuXUv9Q8r828UhrNmuVM Ghw7Aw08uOii6494jCSp1Lg6ltC3uESIcQsQ258ON7FbFohdgwC5uO+UVmrrWAp7alF3 hdAw== X-Gm-Message-State: AOAM532dp15u7VLRU/f10OheyxEeIWmp8INudvAXl1sKSdTx1JdJhowo 6Ht8TFl+9JaOwIu+JLYDX7TYmg== X-Google-Smtp-Source: ABdhPJzhfKc56+AGehB6rwlydFBdwcHeviUbHIFnDTRU6KIyTbtZIkuuDhw1XuIj5pRTYfxo6B4M8Q== X-Received: by 2002:a5e:8c05:: with SMTP id n5mr6480970ioj.0.1636044062919; Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Received: from google.com (194.225.68.34.bc.googleusercontent.com. [34.68.225.194]) by smtp.gmail.com with ESMTPSA id u12sm1074124iop.52.2021.11.04.09.41.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Nov 2021 09:41:02 -0700 (PDT) Date: Thu, 4 Nov 2021 16:40:58 +0000 From: Oliver Upton To: Reiji Watanabe Cc: Marc Zyngier , kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, James Morse , Alexandru Elisei , Suzuki K Poulose , Paolo Bonzini , Will Deacon , Andrew Jones , Peng Liang , Peter Shier , Ricardo Koller , Jing Zhang , Raghavendra Rao Anata Subject: Re: [RFC PATCH v2 18/28] KVM: arm64: Introduce KVM_CAP_ARM_ID_REG_WRITABLE capability Message-ID: References: <20211103062520.1445832-1-reijiw@google.com> <20211103062520.1445832-19-reijiw@google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20211103062520.1445832-19-reijiw@google.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20211104_094103_902303_F0A44E4E X-CRM114-Status: GOOD ( 17.63 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Nov 02, 2021 at 11:25:10PM -0700, Reiji Watanabe wrote: > Introduce a new capability KVM_CAP_ARM_ID_REG_WRITABLE to indicate > that ID registers are writable by userspace. > > Signed-off-by: Reiji Watanabe > --- > Documentation/virt/kvm/api.rst | 8 ++++++++ > arch/arm64/kvm/arm.c | 1 + > include/uapi/linux/kvm.h | 1 + > 3 files changed, 10 insertions(+) > > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst > index a6729c8cf063..f7dfb5127310 100644 > --- a/Documentation/virt/kvm/api.rst > +++ b/Documentation/virt/kvm/api.rst > @@ -7265,3 +7265,11 @@ The argument to KVM_ENABLE_CAP is also a bitmask, and must be a subset > of the result of KVM_CHECK_EXTENSION. KVM will forward to userspace > the hypercalls whose corresponding bit is in the argument, and return > ENOSYS for the others. > + > +8.35 KVM_CAP_ARM_ID_REG_WRITABLE > +-------------------------------- ID registers are technically already writable, KVM just rejects any value other than what it derives from sanitising the host ID registers. I agree that the nuance being added warrants a KVM_CAP, as it informs userspace it can deliberately configure ID registers with a more limited value than what KVM returns. KVM_CAP_ARM_ID_REG_CONFIGURABLE maybe? Naming is hard :) -- Thanks, Oliver _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel