From: Sean Christopherson <seanjc@google.com>
To: Rick P Edgecombe <rick.p.edgecombe@intel.com>
Cc: "jmattson@google.com" <jmattson@google.com>,
Chao Gao <chao.gao@intel.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
Vishal Annapurve <vannapurve@google.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vishal L Verma <vishal.l.verma@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
Erdem Aktas <erdemaktas@google.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable
Date: Wed, 24 Apr 2024 12:57:43 -0700 [thread overview]
Message-ID: <ZilaWM4AmrbeSEy0@google.com> (raw)
In-Reply-To: <6f476d85cdb9dfdc0893e9eb762dca08f0f5f19b.camel@intel.com>
On Wed, Apr 24, 2024, Rick P Edgecombe wrote:
> Long term though, I have been wondering about how to prevent TDX regressions
> especially on the MMU pieces. It is one thing to have the TDX setups available
> for maintainers, but most normal developers will likely not have access to TDX
> HW for a bit. Just a problem without a solution.
I wouldn't worry too much about hardware availability. As you said, it's not
a problem we can really solve, and we already have to be concious of the fact
that not all developers have comparable hardware. E.g. most people don't have
a 4-sock, multi-hundred CPU system with TiBs of RAM. Not being able to test at
all is obviously a little different, but it's not entirely new.
Instead, I would encourage spending time and effort (after things have settled
down patch wise) to build out selftests. I tried to run a "real" SEV-ES VM
and gave up because I needed the "right" OVMF build, blah blah blah. At some
point I'll probably bite the bullet and get a "full" CoCo setup working, but it's
not exactly at the top of my todo list, in no small part because the triage and
debug experience when things go wrong is miles and miles better in selftests.
next prev parent reply other threads:[~2024-04-24 19:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:37 [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable Reinette Chatre
2024-03-21 16:37 ` [PATCH V4 1/4] KVM: x86: hyper-v: Calculate APIC bus frequency for Hyper-V Reinette Chatre
2024-04-16 17:07 ` Edgecombe, Rick P
2024-03-21 16:37 ` [PATCH V4 2/4] KVM: x86: Make nsec per APIC bus cycle a VM variable Reinette Chatre
2024-04-16 17:08 ` Edgecombe, Rick P
2024-03-21 16:37 ` [PATCH V4 3/4] KVM: x86: Add a capability to configure bus frequency for APIC timer Reinette Chatre
2024-04-16 17:08 ` Edgecombe, Rick P
2024-04-16 21:28 ` Reinette Chatre
2024-04-17 3:37 ` Xiaoyao Li
2024-03-21 16:37 ` [PATCH V4 4/4] KVM: selftests: Add test for configure of x86 APIC bus frequency Reinette Chatre
2024-04-16 17:09 ` [PATCH V4 0/4] KVM: x86: Make bus clock frequency for vAPIC timer configurable Edgecombe, Rick P
2024-04-24 16:13 ` Sean Christopherson
2024-04-24 16:38 ` Edgecombe, Rick P
2024-04-24 17:23 ` Sean Christopherson
2024-04-24 18:10 ` Edgecombe, Rick P
2024-04-24 19:57 ` Sean Christopherson [this message]
2024-04-24 21:20 ` Reinette Chatre
2024-04-25 16:17 ` Sean Christopherson
2024-04-25 16:39 ` Reinette Chatre
2024-04-24 21:07 ` Reinette Chatre
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=ZilaWM4AmrbeSEy0@google.com \
--to=seanjc@google.com \
--cc=chao.gao@intel.com \
--cc=erdemaktas@google.com \
--cc=isaku.yamahata@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=rick.p.edgecombe@intel.com \
--cc=vannapurve@google.com \
--cc=vishal.l.verma@intel.com \
--cc=vkuznets@redhat.com \
--cc=xiaoyao.li@intel.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