From: Simon Pilkington <simonp.git@mailbox.org>
To: Sean Christopherson <seanjc@google.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
regressions@lists.linux.dev,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [REGRESSION] from 74a0e79df68a8042fb84fd7207e57b70722cf825: VFIO PCI passthrough no longer works
Date: Tue, 10 Dec 2024 21:33:58 +0100 [thread overview]
Message-ID: <93a3edef-dde6-4ef6-ae40-39990040a497@mailbox.org> (raw)
In-Reply-To: <Z1hiiz40nUqN2e5M@google.com>
On 10/12/2024 16:47, Sean Christopherson wrote:
> Can you run with the below to see what bits the guest is trying to set (or clear)?
> We could get the same info via tracepoints, but this will likely be faster/easier.
>
> ---
> arch/x86/kvm/svm/svm.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index dd15cc635655..5144d0283c9d 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -3195,11 +3195,14 @@ static int svm_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr)
> case MSR_AMD64_DE_CFG: {
> u64 supported_de_cfg;
>
> - if (svm_get_feature_msr(ecx, &supported_de_cfg))
> + if (WARN_ON_ONCE(svm_get_feature_msr(ecx, &supported_de_cfg)))
> return 1;
>
> - if (data & ~supported_de_cfg)
> + if (data & ~supported_de_cfg) {
> + pr_warn("DE_CFG supported = %llx, WRMSR = %llx\n",
> + supported_de_cfg, data);
> return 1;
> + }
>
> /*
> * Don't let the guest change the host-programmed value. The
> @@ -3207,8 +3210,11 @@ static int svm_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr)
> * are completely unknown to KVM, and the one bit known to KVM
> * is simply a reflection of hardware capabilities.
> */
> - if (!msr->host_initiated && data != svm->msr_decfg)
> + if (!msr->host_initiated && data != svm->msr_decfg) {
> + pr_warn("DE_CFG current = %llx, WRMSR = %llx\n",
> + svm->msr_decfg, data);
> return 1;
> + }
>
> svm->msr_decfg = data;
> break;
>
> base-commit: fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
Relevant dmesg output with some context below. VM locked up as expected.
[ 85.834971] vfio-pci 0000:0c:00.0: resetting
[ 85.937573] vfio-pci 0000:0c:00.0: reset done
[ 86.494210] vfio-pci 0000:0c:00.0: resetting
[ 86.494264] vfio-pci 0000:0c:00.1: resetting
[ 86.761442] vfio-pci 0000:0c:00.0: reset done
[ 86.761480] vfio-pci 0000:0c:00.1: reset done
[ 86.762392] vfio-pci 0000:0c:00.0: resetting
[ 86.865462] vfio-pci 0000:0c:00.0: reset done
[ 86.977360] virbr0: port 1(vnet1) entered learning state
[ 88.993052] virbr0: port 1(vnet1) entered forwarding state
[ 88.993057] virbr0: topology change detected, propagating
[ 103.459114] kvm_amd: DE_CFG current = 0, WRMSR = 2
[ 161.442032] virbr0: port 1(vnet1) entered disabled state // VM shut down
next prev parent reply other threads:[~2024-12-10 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 9:04 [REGRESSION] from 74a0e79df68a8042fb84fd7207e57b70722cf825: VFIO PCI passthrough no longer works Simon Pilkington
2024-12-10 15:47 ` Sean Christopherson
2024-12-10 16:15 ` Tom Lendacky
2024-12-10 20:33 ` Simon Pilkington [this message]
2024-12-10 21:06 ` Tom Lendacky
2024-12-10 22:43 ` Sean Christopherson
2024-12-11 8:54 ` Simon Pilkington
2024-12-11 14:37 ` Tom Lendacky
2024-12-11 17:42 ` Simon Pilkington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93a3edef-dde6-4ef6-ae40-39990040a497@mailbox.org \
--to=simonp.git@mailbox.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox