From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (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 22433176FD3 for ; Tue, 27 Aug 2024 09:06:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.46 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1724749580; cv=none; b=OOWjmzh0UusD599G7V5oxtQwtHVmllYn11/If8eFP5/w0rMNVTww3MrDtY18ycgWbW8WkDuhMkQMdYNShyg2lZ0ZMimwzAEUV95ONmJEZN+zfSBdfJ4Ce0j+1pWX7axba4KxpCanNW2Tx7zVIbr+4tEfgG8IQvlzwVhr1WuJsPc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1724749580; c=relaxed/simple; bh=td6TsY+x1jF2bYWtgW1QVma5ZvKvJwuhzTvVDhTcxRU=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=dNvrn/T7PnRGiNjMz3FFUdQUQW5K459vy2vGdHZaHxylVd+A6HAiyNna/CJtpUQWTGt6VZoLI34qPBsKGgnPjaAWWrM9cf8+GtgeksXzP7N6z7RiOBlhPrsaVBQhEPV3ucjj3uWU6yWmS5a6SMJkBHkIA7tnQ+VyueWwOHPtA2c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=b25Gnzx/; arc=none smtp.client-ip=209.85.221.46 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="b25Gnzx/" Received: by mail-wr1-f46.google.com with SMTP id ffacd0b85a97d-371b015572cso3821578f8f.1 for ; Tue, 27 Aug 2024 02:06:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1724749576; x=1725354376; darn=lists.linux.dev; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=ys5q7+xt7V4u8ZvUMbFPxHX+g0yKhziPVMVNXUTaajE=; b=b25Gnzx/5ImiEj6Cnq6tTZzD9X9E6P7hyRY1sAFRyQi0Kvn7+CZmnTI83imZeuPc9e w0+JTkwhS3zojb8dqoQwnmb7ukSPQ6lS8V8woYAA8MTCKJMh+HSPkyiJi216NyZ/49Zd Zy+yNhiR5Fdo0swMyvlLgvZtTgniRuH5ei7INPJshfQfkBDjqk0W3iZa7HYsT+WOaQfb GJkMwT9uPf9lGDGEraTCMOqcWTQ5ca8MuqTlDpu9ZSeBeEtvn+ttiW/qorWR+YaPOrs8 O8+KIOnGIXDGuwmouvAKhzrtxcwIWbCnwQprAWN49Po08AWmDSb3HTJ9q3d1XnbVxk71 JQ0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724749576; x=1725354376; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ys5q7+xt7V4u8ZvUMbFPxHX+g0yKhziPVMVNXUTaajE=; b=bLS8lHYI3GHXzXc+kfBI0eu7oteFCmS2QDZONpeq7IElWDuDd6+VU9hMyxDTGnPdQ8 YOQGf50xiSjoPANLg/AXDuK0sHCo08A943FBEFElQjxYRn5MVdzpREXzovEhWlFTTBNp yS18GAI6KL878whpOLsNiU/VC1sNmoeKnUDnQ78FunF0eJWvqKHdH0nWIG6IoBqrugl7 7oWqRboDjlQHSxp0mqYULTcqhA2PIYMQQivCbgnuEDyL9Jnjzgk/BlQGwXkTVbOcfVTB XcqPjZ/guchwAN6JpcGbSRHJosz20M1f8FIES4Gg0a0xJahksstV9mis0ZSxKxiiLcKO b7JQ== X-Forwarded-Encrypted: i=1; AJvYcCUkA0W4GeGQ4gAQUtzzr1/ZCsIm8DYdeqEfFIPRq0Pd1iLw9/MlvikzSFP4NMFGxEd+jGUmlAg=@lists.linux.dev X-Gm-Message-State: AOJu0YxVJyZee+t5vzor3B61luBZXRJK8vx7WHVN4LbFhILGWRX+Qk5x g19tPdV9xVnkLMcZfWXmYr+fRb1eI3MDHmwNljJ9xgVYrsngzLjQfLH8yaKNWN4= X-Google-Smtp-Source: AGHT+IE+VDn5FOe01bWlunlr3Q/efu0PB9LC4RFl5VPjT0A0kz6PEXEkfZYstnAt53OJLkCDA/f1HA== X-Received: by 2002:adf:b311:0:b0:368:3f6a:1dea with SMTP id ffacd0b85a97d-37311840050mr9300691f8f.6.1724749575912; Tue, 27 Aug 2024 02:06:15 -0700 (PDT) Received: from draig.lan ([85.9.250.243]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-3730826a3f7sm12533503f8f.112.2024.08.27.02.06.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Aug 2024 02:06:15 -0700 (PDT) Received: from draig (localhost [IPv6:::1]) by draig.lan (Postfix) with ESMTP id 507E15F7A2; Tue, 27 Aug 2024 10:06:14 +0100 (BST) From: =?utf-8?Q?Alex_Benn=C3=A9e?= To: Sean Christopherson Cc: Paolo Bonzini , Marc Zyngier , Oliver Upton , Tianrui Zhao , Bibo Mao , Huacai Chen , Michael Ellerman , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank , Claudio Imbrenda , kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, loongarch@lists.linux.dev, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, David Matlack , David Stevens Subject: Re: [PATCH v12 00/84] KVM: Stop grabbing references to PFNMAP'd pages In-Reply-To: <20240726235234.228822-1-seanjc@google.com> (Sean Christopherson's message of "Fri, 26 Jul 2024 16:51:09 -0700") References: <20240726235234.228822-1-seanjc@google.com> Date: Tue, 27 Aug 2024 10:06:14 +0100 Message-ID: <875xrme3nd.fsf@draig.linaro.org> Precedence: bulk X-Mailing-List: kvmarm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sean Christopherson writes: > arm64 folks, the first two patches are bug fixes, but I have very low > confidence that they are correct and/or desirable. If they are more or > less correct, I can post them separately if that'd make life easier. I > included them here to avoid conflicts, and because I'm pretty sure how > KVM deals with MTE tags vs. dirty logging will impact what APIs KVM needs > to provide to arch code. > > On to the series... The TL;DR is that I would like to get input on two > things: > > 1. Marking folios dirty/accessed only on the intial stage-2 page fault > 2. The new APIs for faulting, prefetching, and doing "lookups" on > pfns I've finally managed to get virtio-vulkan working on my Arm64 devbox with an AMD graphics card plugged into the PCI. I'm confident that the graphics path is using the discrete card memory (as it has been mapped as device memory with alignment handlers to deal with the broken Altra PCI). However aside from running graphics workloads in KVM guests is their anything else I can check to see things are behaving as expected? The predecessor series did break launching some KVM guests on my x86 system but with this series launching guests works fine and I haven't noticed any weirdness. So for those caveats you can certainly have a: Tested-by: Alex Benn=C3=A9e However if there is anything else I can do to further stress test this code do let me know. --=20 Alex Benn=C3=A9e Virtualisation Tech Lead @ Linaro