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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 5FC7AE7717F for ; Mon, 16 Dec 2024 22:34:36 +0000 (UTC) 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:To:From:Subject:Message-ID:References: Mime-Version:In-Reply-To:Date:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=OKYZ3twjaxmOnK52J1KIuCD7rHiCekjDTueU3xr/GVg=; b=rGiUmLXSUW2OUf 3biCIkNXSSPOW2CxNAdG9mvHGSg+3Oe+MJ2lD52kyNDzhC2ms+H+/bjePOQG2bXP9ARgJJiyouxsH t/nSmAzOLXyvQ/AyDUFfi49IGEmLMBxfFn7he2v/FVm2cahYRral9CrboR7HVCFVHQdMpmSmNjE/b YZxrLYBWamsJ9jbMonEWnVwEI86XmiAYRTG7fpPHLno8l2KE+3xuCb2KNFvLyUCKqioQzQF9tPNSP 2AoZEy9vRFA3+BmP8MqbPU0hjF4njo5AkC4B3rYqCBi/qJ4AjSsfJ7mlK2Ee2Hm93Ev6g4clcLUEe el+a9iBH8Az1aMFDD+Rg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1tNJff-0000000BZt5-3jkQ; Mon, 16 Dec 2024 22:34:35 +0000 Received: from mail-pj1-x1049.google.com ([2607:f8b0:4864:20::1049]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1tNJea-0000000BZfO-1rZ9 for kvm-riscv@lists.infradead.org; Mon, 16 Dec 2024 22:33:30 +0000 Received: by mail-pj1-x1049.google.com with SMTP id 98e67ed59e1d1-2eedd15c29eso4065637a91.3 for ; Mon, 16 Dec 2024 14:33:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1734388406; x=1734993206; darn=lists.infradead.org; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=Lj1bwB5qFVVYl6V4ofAH8DiHbhJjjKmkd3/tXkieDtcGyUbOMHSxnxQMOwHb4O1/W4 /UH0jEg1mw1+1hpFXy4DBXhPydOlgQAPBpRZFJcygvFeDvSghE0iN0pyqG63OCXY2ld9 KJ1vyMAoV8RWXL8+yjb1cUYJauX5BogoDlKlv0U2dZnplaXnOJn9mH5u/jjIPhYAVBOX wjs50RokXxtn02ZRKT0tEWoxipntZIxoO1lmzYFNWcZuyXOJdAEfl0vEaj88jGsEOx4V AWXKCAf5uEJerylMYLtfkPYv1cnygP9Opf+BUR1gpfTdS4w6tOKVPeTWRpAt/RSLnaWv gCyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734388406; x=1734993206; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=SetbJL+800vvNX95Am9REo7XjOomJqXpsv5xpGTqpmdyhHRVgB0i3qeDJrVJ136ILC WgcH+LOWY8NKGhTUsObVY3JgIHFLOmAxoSDVsG7+hDETVuTKOtrJYNdJqfPjaja4x/I+ pweCIKvURdpNt5E3ADyRPD4uiB+tpswpt3fYwccwOQMH1IOe4B7EzPpn0J0xvyJa1FA5 Cv1/jnsJQtNHbsKDP01FqJkhL8328b9cdbK+UUnIBbAtlPgfhbVBdyhfcebppNm7uuLD euaUA7JURSY1pCE9b4U40WTRIUvwxCu+UXVZ5isRrkUcoNTeeg9cMT4bP4JjugUIXfSF PSJw== X-Forwarded-Encrypted: i=1; AJvYcCVQNVhoH7JHhIUcBAxGSYL3BGwow0fUT3FPWix+mdFx0AjhIfSve3FHTNZc9TCCEZmocYIKN6AiLJQ=@lists.infradead.org X-Gm-Message-State: AOJu0YwZd+fLgNO6jFqnpDDwtztIgE7RsVxrh2z3ndG3bJtkmxq1l5UI L+nqG5S2SMJkrXXiEioIGkyucTmi53M319MjP7ivGCapqkLemb7GJe9R8npFujEbxrVyaHg1HXN auA== X-Google-Smtp-Source: AGHT+IHhtWHdid0XDbI59B1aoA+CN7rFIH/zmVAk3APPQqAwY7oJZB6TaL0aH/5JThWes+dWQrGdtB7EGl0= X-Received: from pjd5.prod.google.com ([2002:a17:90b:54c5:b0:2ef:8eb8:e4eb]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a17:90a:c887:b0:2ee:6e22:bfd0 with SMTP id 98e67ed59e1d1-2f2d7eece80mr1530327a91.21.1734388406334; Mon, 16 Dec 2024 14:33:26 -0800 (PST) Date: Mon, 16 Dec 2024 14:33:24 -0800 In-Reply-To: <20241128005547.4077116-1-seanjc@google.com> Mime-Version: 1.0 References: <20241128005547.4077116-1-seanjc@google.com> Message-ID: Subject: Re: [PATCH v4 00/16] KVM: selftests: "tree" wide overhauls From: Sean Christopherson To: Marc Zyngier , Oliver Upton , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Paolo Bonzini , Christian Borntraeger , Janosch Frank , Claudio Imbrenda , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Andrew Jones , James Houghton , Muhammad Usama Anjum X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241216_143328_473872_BA7E114F X-CRM114-Status: GOOD ( 15.23 ) X-BeenThere: kvm-riscv@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: "kvm-riscv" Errors-To: kvm-riscv-bounces+kvm-riscv=archiver.kernel.org@lists.infradead.org On Wed, Nov 27, 2024, Sean Christopherson wrote: > Two separate series (mmu_stress_test[1] and $ARCH[2]), posted as one to > avoid unpleasant conflicts, and because I hope to land both in kvm/next > shortly after 6.12-rc1 since they impact all of KVM selftests. > > mmu_stress_test > --------------- > Convert the max_guest_memory_test into a more generic mmu_stress_test. > The basic gist of the "conversion" is to have the test do mprotect() on > guest memory while vCPUs are accessing said memory, e.g. to verify KVM > and mmu_notifiers are working as intended. > > The original plan was that patch 3 would be a single patch, but things > snowballed in order to rework vcpu_get_reg() to return a value instead > of using an out-param. Having to define a variable just to bump the > program counter on arm64 annoyed me. > > $ARCH > ----- > Play nice with treewrite builds of unsupported architectures, e.g. arm > (32-bit), as KVM selftests' Makefile doesn't do anything to ensure the > target architecture is actually one KVM selftests supports. > > The last two patches are opportunistic changes (since the above Makefile > change will generate conflicts everywhere) to switch to using $(ARCH) > instead of the target triple for arch specific directories, e.g. arm64 > instead of aarch64, mainly so as not to be different from the rest of > the kernel. Paolo, Unless you or someone else have concerns, can you apply this to kvm/next sooner than later? I'd like to start applying selftests changes for 6.14 and don't want generate conflicts, and I really don't want to have to rebase and push this series out again. Thanks! -- kvm-riscv mailing list kvm-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kvm-riscv From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f74.google.com (mail-pj1-f74.google.com [209.85.216.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1280E1D63D0 for ; Mon, 16 Dec 2024 22:33:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.74 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734388408; cv=none; b=nahdPho6F1UpzcLQmHlbotbyUHbV4Vpok1gMOV7BZDQcbprd8WZ3bPQV9K8H2DiNqXldtwG+mchzB0w+CdsFJ6F7acJimMTJa1jC5aLMUGET8icyFBZ9Nx2Q3bzFK9rsHMJ3zE12YMnXcjR/Wgp4THehJxKZoBg+k01iyCdTz9A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734388408; c=relaxed/simple; bh=AQ6L0FE4N7ae+Cg2Eu7wbgOie9mHJiVhQr34moiqfqI=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Content-Type; b=RVBr1YMstbHizWKDqlM28A9i/DGildA+WpkE3jw0GK7r4ZU0d4So8iP6wA/H6Qzc2xAahlVfQ25X7NBQSbUolXh5K7HEQclx7MwI/yWO/Ny4/9+IECTEKrjPQXaKsSRJrYQd3yTTCQWHLKy6mDlrCGjz7/ufmTOZW3X6/QrOKm0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=bUgJRyml; arc=none smtp.client-ip=209.85.216.74 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="bUgJRyml" Received: by mail-pj1-f74.google.com with SMTP id 98e67ed59e1d1-2ee86953aeaso4067022a91.2 for ; Mon, 16 Dec 2024 14:33:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1734388406; x=1734993206; darn=vger.kernel.org; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=bUgJRymlxUYtLkubw2seHPAskoB6hY8bgUddpHzw1r6UwGxxMKD3Jtf8AfaAPrIu1n 73jHT+y6D8Z8QfDC2wqSVn9L0nSFBnhkO2HK0lrmhwkuGBpM10ecYCQN+aVg3Bh9q81n 4jyfGxceCKVMKZw0LirEBk+iYusKf5bFAzigNM+Nuq8vZAhEWEZIRomgUHhLpmy0njKT Ga6kWyQZ95nn6fp0gbU4IUIDDStPM1ol56mXtBY4tHpkXrFdKK/trrddUY1VyU8nMQ3R xWUAz9PiZeGC6gxn0N1pd+f9jrh8uYyvrkeqEedR2+S4NkWh3AcYHL/mcAiQf0cTkfuD eLuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734388406; x=1734993206; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=UY+bo06cv+b7uFgpQ8UfrUQ6QiCAUcxDKRHCGEEEscD24tvMREeZgCRh9p8eeYwmES J3fdPTvSmCqOuFX5YM7V1kOPL0PpL1Cob3L+pcpDXcddwj7ej9FzwuiT88KRa78p65XP 7uvR65DSRTUIbHvt+DOOEi1WbV8/aztoHQ1Ke0B1wE0lFVRwIAnpmjtGENzOyj6IW9af Z8uqvYNEOIao2sGTW9OIXc7QnOVIUZJFtEbvYuDfZg59UWrbl5iDNV+6FSf5/81HsrM7 XyeJ+iQz2lXGYsrPJvCdubv95KqrOJPTfGnPNv3VN5IQWbPghM3HB6KfEzqPLVJtkzz2 l0vQ== X-Forwarded-Encrypted: i=1; AJvYcCVerJe4gDDeCnd2i2reie/ChVpUjBkDzackiNO6eJB/fJw5is7yX+SDMjQarm6V65jiUjo=@vger.kernel.org X-Gm-Message-State: AOJu0YwWtwp5IWWrrQx2qA8DVpccqFQKIgNnVG77bBChimvi22w3zg2d eusp4Jl7HCFUOtEJ8YCVepaTOGgvr8Q1trX2yvWoXlsX10gu85is6y06s5+z0u6pCKh6uflskbg pPw== X-Google-Smtp-Source: AGHT+IHhtWHdid0XDbI59B1aoA+CN7rFIH/zmVAk3APPQqAwY7oJZB6TaL0aH/5JThWes+dWQrGdtB7EGl0= X-Received: from pjd5.prod.google.com ([2002:a17:90b:54c5:b0:2ef:8eb8:e4eb]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a17:90a:c887:b0:2ee:6e22:bfd0 with SMTP id 98e67ed59e1d1-2f2d7eece80mr1530327a91.21.1734388406334; Mon, 16 Dec 2024 14:33:26 -0800 (PST) Date: Mon, 16 Dec 2024 14:33:24 -0800 In-Reply-To: <20241128005547.4077116-1-seanjc@google.com> Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20241128005547.4077116-1-seanjc@google.com> Message-ID: Subject: Re: [PATCH v4 00/16] KVM: selftests: "tree" wide overhauls From: Sean Christopherson To: Marc Zyngier , Oliver Upton , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Paolo Bonzini , Christian Borntraeger , Janosch Frank , Claudio Imbrenda , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Andrew Jones , James Houghton , Muhammad Usama Anjum Content-Type: text/plain; charset="us-ascii" On Wed, Nov 27, 2024, Sean Christopherson wrote: > Two separate series (mmu_stress_test[1] and $ARCH[2]), posted as one to > avoid unpleasant conflicts, and because I hope to land both in kvm/next > shortly after 6.12-rc1 since they impact all of KVM selftests. > > mmu_stress_test > --------------- > Convert the max_guest_memory_test into a more generic mmu_stress_test. > The basic gist of the "conversion" is to have the test do mprotect() on > guest memory while vCPUs are accessing said memory, e.g. to verify KVM > and mmu_notifiers are working as intended. > > The original plan was that patch 3 would be a single patch, but things > snowballed in order to rework vcpu_get_reg() to return a value instead > of using an out-param. Having to define a variable just to bump the > program counter on arm64 annoyed me. > > $ARCH > ----- > Play nice with treewrite builds of unsupported architectures, e.g. arm > (32-bit), as KVM selftests' Makefile doesn't do anything to ensure the > target architecture is actually one KVM selftests supports. > > The last two patches are opportunistic changes (since the above Makefile > change will generate conflicts everywhere) to switch to using $(ARCH) > instead of the target triple for arch specific directories, e.g. arm64 > instead of aarch64, mainly so as not to be different from the rest of > the kernel. Paolo, Unless you or someone else have concerns, can you apply this to kvm/next sooner than later? I'd like to start applying selftests changes for 6.14 and don't want generate conflicts, and I really don't want to have to rebase and push this series out again. Thanks! 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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id E6F87E7717F for ; Mon, 16 Dec 2024 22:33:37 +0000 (UTC) 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:To:From:Subject:Message-ID:References: Mime-Version:In-Reply-To:Date:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=YIJVVg5U1vU11oo1F4GxHHoxDyKCOIDrLGG0SIyPh/k=; b=IyZWNhH2DoL3LT HvfxGq2YElQzIWrrSQF+pINbKH8++UA4cu/1bxULgUoNd3ITdYsA8ZFTlOL1NkiAeMidFdrZxUsS+ EJKL4SAipp+/IxzDXN6JdjIOQJoM9WAqNvG0dBHiB9SoZIC0hSQzpibQNqty0fZKzt3ZXtDdyVYoL 0kvzBneQkf7SenKk7GjJER0HwChCG2woYd29774gvSVbifSuHXdiwn5TgsGpzOangVPPj6v1dEA7b XiQv7xA71J7vscM8Lf3DhSN2cp871aFoGvNIPas5cV7XCapc8rF8RyyDkspyy1p+7iSL7+1rw7Tne qBOmkTJIoNZHlnmECr5w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1tNJec-0000000BZgQ-2vip; Mon, 16 Dec 2024 22:33:30 +0000 Received: from mail-pj1-x1049.google.com ([2607:f8b0:4864:20::1049]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1tNJea-0000000BZfN-0dlR for linux-riscv@lists.infradead.org; Mon, 16 Dec 2024 22:33:29 +0000 Received: by mail-pj1-x1049.google.com with SMTP id 98e67ed59e1d1-2ee86953aeaso4067023a91.2 for ; Mon, 16 Dec 2024 14:33:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1734388406; x=1734993206; darn=lists.infradead.org; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=Lj1bwB5qFVVYl6V4ofAH8DiHbhJjjKmkd3/tXkieDtcGyUbOMHSxnxQMOwHb4O1/W4 /UH0jEg1mw1+1hpFXy4DBXhPydOlgQAPBpRZFJcygvFeDvSghE0iN0pyqG63OCXY2ld9 KJ1vyMAoV8RWXL8+yjb1cUYJauX5BogoDlKlv0U2dZnplaXnOJn9mH5u/jjIPhYAVBOX wjs50RokXxtn02ZRKT0tEWoxipntZIxoO1lmzYFNWcZuyXOJdAEfl0vEaj88jGsEOx4V AWXKCAf5uEJerylMYLtfkPYv1cnygP9Opf+BUR1gpfTdS4w6tOKVPeTWRpAt/RSLnaWv gCyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734388406; x=1734993206; h=to:from:subject:message-id:references:mime-version:in-reply-to:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9jJCzoGzQp+cdjga58qGUwc3ffJR9vhNALvR1f7QLKI=; b=AjB5SbWJRB57Fle3Kf3v2IZmEm7ETlHhbHZ55/ZC4wL25Ih4cw2BEZbvAZaUfBP1VX zIXKeELTjjBzJu4mcPgRyNexRbZ13O7s8tOXWGUCmY8OR3K7i+xq2XXW4cf6LPH5pZiJ jD/SOP0z2xPunmeVKJ2ZAkrU4kAKvKlGOX92WAWPN8w3xwVaIFfWBATgasxycw/j+kwR 4cZuLPgcNzB+18C8kJIyF4uP65yGpeVGpNouUUpf0SdH9ZfGNFcZyuYZNTUsWFhDhy7t hxpA0LDKY/3J7y/gsjchPPC79ohHM/FzOG6JFmRMCtoyVcyEFdYdv6DLeB9Ra/8I3v78 cbcQ== X-Forwarded-Encrypted: i=1; AJvYcCVfjEYI8k5CdFAjOIzSyn4J/iZ2g+NGPvlYnbu15uppeuMqp4DLnEj2JrJOiWgQqRIDtp2OQwiDzwOkUA==@lists.infradead.org X-Gm-Message-State: AOJu0YxaMo/JV0vaMdIVn84NOoSH7o7zrQ7TthqdE9hxUJW1IanSXYnZ suy4N2qJV5I8WsbxxA7E5a4QHQmA1Ci+x7FLmxGTUVLis1JpPQEnOehqLlDZQZe3DpMgs/+ldPu 8tg== X-Google-Smtp-Source: AGHT+IHhtWHdid0XDbI59B1aoA+CN7rFIH/zmVAk3APPQqAwY7oJZB6TaL0aH/5JThWes+dWQrGdtB7EGl0= X-Received: from pjd5.prod.google.com ([2002:a17:90b:54c5:b0:2ef:8eb8:e4eb]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a17:90a:c887:b0:2ee:6e22:bfd0 with SMTP id 98e67ed59e1d1-2f2d7eece80mr1530327a91.21.1734388406334; Mon, 16 Dec 2024 14:33:26 -0800 (PST) Date: Mon, 16 Dec 2024 14:33:24 -0800 In-Reply-To: <20241128005547.4077116-1-seanjc@google.com> Mime-Version: 1.0 References: <20241128005547.4077116-1-seanjc@google.com> Message-ID: Subject: Re: [PATCH v4 00/16] KVM: selftests: "tree" wide overhauls From: Sean Christopherson To: Marc Zyngier , Oliver Upton , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Paolo Bonzini , Christian Borntraeger , Janosch Frank , Claudio Imbrenda , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Andrew Jones , James Houghton , Muhammad Usama Anjum X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241216_143328_183548_DC71E484 X-CRM114-Status: GOOD ( 15.23 ) X-BeenThere: linux-riscv@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-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On Wed, Nov 27, 2024, Sean Christopherson wrote: > Two separate series (mmu_stress_test[1] and $ARCH[2]), posted as one to > avoid unpleasant conflicts, and because I hope to land both in kvm/next > shortly after 6.12-rc1 since they impact all of KVM selftests. > > mmu_stress_test > --------------- > Convert the max_guest_memory_test into a more generic mmu_stress_test. > The basic gist of the "conversion" is to have the test do mprotect() on > guest memory while vCPUs are accessing said memory, e.g. to verify KVM > and mmu_notifiers are working as intended. > > The original plan was that patch 3 would be a single patch, but things > snowballed in order to rework vcpu_get_reg() to return a value instead > of using an out-param. Having to define a variable just to bump the > program counter on arm64 annoyed me. > > $ARCH > ----- > Play nice with treewrite builds of unsupported architectures, e.g. arm > (32-bit), as KVM selftests' Makefile doesn't do anything to ensure the > target architecture is actually one KVM selftests supports. > > The last two patches are opportunistic changes (since the above Makefile > change will generate conflicts everywhere) to switch to using $(ARCH) > instead of the target triple for arch specific directories, e.g. arm64 > instead of aarch64, mainly so as not to be different from the rest of > the kernel. Paolo, Unless you or someone else have concerns, can you apply this to kvm/next sooner than later? I'd like to start applying selftests changes for 6.14 and don't want generate conflicts, and I really don't want to have to rebase and push this series out again. Thanks! _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv