Message ID | 20221130230934.1014142-1-seanjc@google.com |
---|---|
Headers | show
Return-Path: <kvm-riscv-bounces+incoming=patchwork.ozlabs.org@lists.infradead.org> X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=lists.infradead.org (client-ip=2607:7c80:54:3::133; helo=bombadil.infradead.org; envelope-from=kvm-riscv-bounces+incoming=patchwork.ozlabs.org@lists.infradead.org; receiver=<UNKNOWN>) Authentication-Results: legolas.ozlabs.org; dkim=pass (2048-bit key; secure) header.d=lists.infradead.org header.i=@lists.infradead.org header.a=rsa-sha256 header.s=bombadil.20210309 header.b=GoPFHEqN; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20210112 header.b=a3LNmo1f; dkim-atps=neutral Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4NMvzx0QSCz23nB for <incoming@patchwork.ozlabs.org>; Thu, 1 Dec 2022 10:09:48 +1100 (AEDT) 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:Reply-To:List-Subscribe:List-Help: List-Post:List-Archive:List-Unsubscribe:List-Id:Cc:To:From:Subject:Message-ID :Mime-Version:Date:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=89jkDIRoXvefx0fKcTIF9TwvYaV6QLByuvmlCrGJVgM=; b=GoPFHEqNzjUxzn Z4ihj2/EgcOgXCrtvawY63oZ5WZ8+xS8OC4OPIT1NrxkEunv/vBip3ldEkippjnOciXxU92AsyKM2 3WRvz+J9zQhf8zudeKoQvYdkIRlsOnGJ6dNtLmM8v1aLb7GiWjXJqOVVufmvlyi73BGlo8fr95scE O3qj2KycatjxplPy/EK2wG8wYD8Y0Xrrs2OMkywwiV05ESMOnh/E5enS3rWhCQnVRBcrwKZC0Nrul MzAy4yFdQc3iwYLxIAEkPNbMQbKMGfeouPhqZXEPJJOoo5s5BAdvW1IX8czrRRpu87BejFYV3kk2U d0JynuUyMCC50K6+Re1Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1p0WD2-00366R-0a; Wed, 30 Nov 2022 23:09:44 +0000 Received: from mail-pl1-x64a.google.com ([2607:f8b0:4864:20::64a]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1p0WCx-00362P-QZ for kvm-riscv@lists.infradead.org; Wed, 30 Nov 2022 23:09:41 +0000 Received: by mail-pl1-x64a.google.com with SMTP id m1-20020a170902db0100b00188eec2726cso19122743plx.18 for <kvm-riscv@lists.infradead.org>; Wed, 30 Nov 2022 15:09:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:reply-to:from:to:cc :subject:date:message-id:reply-to; bh=CxJchv8w1iq7EI5igyAbJTSsU4rb9hheWhh1V02wYeE=; b=a3LNmo1flE5DbpWhkEfKOfijpJqR9S7z2ss5lTAXom8sc4KYW3A+wJ62ZtRJGQ4AoH ctdODyVfSXwDyI3Bv7a8JwJ1FhRH869HbxyE8zE9pyL5mb2FzwKcVwcg07F78QqGActo D4bdJlDsk5EpwK/d4RaKsR9vTxEZp18/M1t5bQC30Egg4QdmhW+s2tNgqmbihdq/UwiD FN4aU8sN7cmjq+SKY/1BxqxDWLBu9QzoN5ztRC7YjXsJAs8OnqzJI0tqfNr9g+2FdjL1 ODruZdufVqi1OE3k8wpIrjPjF6wkPtmnuBJ15rRamfG5u6fcCh6JB0zwg9ZckNhELRys CMIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:reply-to :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CxJchv8w1iq7EI5igyAbJTSsU4rb9hheWhh1V02wYeE=; b=u1ubJ3aybQEpNpF7lqDWFI7+w4VjRet9f9SmTyz3a5g02yx+jvErBpey973s6IPit/ yR0mljJrUqb6xHL0E6k6FWsI9EEKrdBY2iF+pxyj1CP230l/YiqO2KXTwnGb0cyysJPN S9/8EVup1qwREkLH4Sn5Hq+qNF/lOQ8MoRojat5yUMQzvDPsk1qbIJfgL5Tm6tpqvAPj ZInm0FB3CR9M9Nf6TWYdE0Le/9tI9rurrCHmvE+T6sYLLnZYRbSAqCwTsTk9/d73N/Yl 3dJjMsgukhk9Bj4XPziC008LoSLwBPWflGXB276l6x4oFeVoWbYx6QasUQI+JOFRjV5D luNQ== X-Gm-Message-State: ANoB5plTQmeWBJMZu/OhPBWmStigFOfVVng+/QYBd0BQFrJpStKFojQQ 6y9l4Ru9juutLbhakbnbLRElkuV4rGI= X-Google-Smtp-Source: AA0mqf4cvJgRHVILOFqJAxbUe/KZulSEyOFrGnuPDy5YFKhx7I74z3MH7FVcVoacDTZw1v9u2COOw/1NyPw= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:7e0e:b0:189:9284:2138 with SMTP id b14-20020a1709027e0e00b0018992842138mr14446370plm.90.1669849777249; Wed, 30 Nov 2022 15:09:37 -0800 (PST) Date: Wed, 30 Nov 2022 23:08:44 +0000 Mime-Version: 1.0 X-Mailer: git-send-email 2.38.1.584.g0f3c55d4c2-goog Message-ID: <20221130230934.1014142-1-seanjc@google.com> Subject: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling From: Sean Christopherson <seanjc@google.com> To: Paolo Bonzini <pbonzini@redhat.com>, Marc Zyngier <maz@kernel.org>, Huacai Chen <chenhuacai@kernel.org>, Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>, Anup Patel <anup@brainfault.org>, Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu>, Christian Borntraeger <borntraeger@linux.ibm.com>, Janosch Frank <frankja@linux.ibm.com>, Claudio Imbrenda <imbrenda@linux.ibm.com>, Matthew Rosato <mjrosato@linux.ibm.com>, Eric Farman <farman@linux.ibm.com>, Sean Christopherson <seanjc@google.com>, Vitaly Kuznetsov <vkuznets@redhat.com>, David Woodhouse <dwmw2@infradead.org>, Paul Durrant <paul@xen.org> Cc: James Morse <james.morse@arm.com>, Alexandru Elisei <alexandru.elisei@arm.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, Oliver Upton <oliver.upton@linux.dev>, Atish Patra <atishp@atishpatra.org>, David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, Yuan Yao <yuan.yao@intel.com>, Cornelia Huck <cohuck@redhat.com>, Isaku Yamahata <isaku.yamahata@intel.com>, " =?utf-8?q?Philippe_Mathieu-Da?= =?utf-8?q?ud=C3=A9?= " <philmd@linaro.org>, Fabiano Rosas <farosas@linux.ibm.com>, Michael Ellerman <mpe@ellerman.id.au>, Kai Huang <kai.huang@intel.com>, Chao Gao <chao.gao@intel.com>, Thomas Gleixner <tglx@linutronix.de> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221130_150939_888743_EB8A7B5F X-CRM114-Status: GOOD ( 16.52 ) X-Spam-Score: -7.7 (-------) X-Spam-Report: Spam detection software, running on the system "bombadil.infradead.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: The main theme of this series is to kill off kvm_arch_init(), kvm_arch_hardware_(un)setup(), and kvm_arch_check_processor_compat(), which all originated in x86 code from way back when, and needlessly [...] Content analysis details: (-7.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2607:f8b0:4864:20:0:0:0:64a listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -7.5 USER_IN_DEF_DKIM_WL From: address is in the default DKIM white-list -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.0 DKIMWL_WL_MED DKIMwl.org - Medium trust sender X-BeenThere: kvm-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: <kvm-riscv.lists.infradead.org> List-Unsubscribe: <http://lists.infradead.org/mailman/options/kvm-riscv>, <mailto:kvm-riscv-request@lists.infradead.org?subject=unsubscribe> List-Archive: <http://lists.infradead.org/pipermail/kvm-riscv/> List-Post: <mailto:kvm-riscv@lists.infradead.org> List-Help: <mailto:kvm-riscv-request@lists.infradead.org?subject=help> List-Subscribe: <http://lists.infradead.org/mailman/listinfo/kvm-riscv>, <mailto:kvm-riscv-request@lists.infradead.org?subject=subscribe> Reply-To: Sean Christopherson <seanjc@google.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kvm-riscv" <kvm-riscv-bounces@lists.infradead.org> Errors-To: kvm-riscv-bounces+incoming=patchwork.ozlabs.org@lists.infradead.org |
Series |
KVM: Rework kvm_init() and hardware enabling
|
expand
|
On Wed, Nov 30, 2022 at 11:08:44PM +0000, Sean Christopherson wrote: >The main theme of this series is to kill off kvm_arch_init(), >kvm_arch_hardware_(un)setup(), and kvm_arch_check_processor_compat(), which >all originated in x86 code from way back when, and needlessly complicate >both common KVM code and architecture code. E.g. many architectures don't >mark functions/data as __init/__ro_after_init purely because kvm_init() >isn't marked __init to support x86's separate vendor modules. Applied this series and verified that an attempt to online incompatible CPUs (no VMX support) when some VMs are running will fail.
Queued, thanks. I will leave this in kvm/queue after testing everything else and moving it to kvm/next; this way, we can wait for test results on other architectures. Paolo
On 2022-12-27 13:02, Paolo Bonzini wrote: > Queued, thanks. I will leave this in kvm/queue after testing > everything > else and moving it to kvm/next; this way, we can wait for test results > on other architectures. Can you please make this a topic branch, and if possible based on a released -rc? It would make it a lot easier for everyone. Thanks, M.
On 12/28/22 12:22, Marc Zyngier wrote: > >> Queued, thanks. I will leave this in kvm/queue after testing everything >> else and moving it to kvm/next; this way, we can wait for test results >> on other architectures. > > Can you please make this a topic branch, and if possible based > on a released -rc? It would make it a lot easier for everyone. Yes, I will (it will be based on 6.2-rc1 + pull request for rc2 that I'm preparing + x86 changes that this conflicts with). Paolo
On 12/28/22 12:22, Marc Zyngier wrote: > >> Queued, thanks. I will leave this in kvm/queue after testing everything >> else and moving it to kvm/next; this way, we can wait for test results >> on other architectures. > > Can you please make this a topic branch, and if possible based > on a released -rc? It would make it a lot easier for everyone. This is now refs/heads/kvm-hw-enable-refactor in https://git.kernel.org/pub/scm/virt/kvm/kvm.git. The commits for this series start at hash fc471e831016. Paolo