From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] Documentation: KVM: KVM_GET_SUPPORTED_CPUID now exposes TSC_DEADLINE
Date: Mon, 31 Mar 2025 12:13:42 -0700 [thread overview]
Message-ID: <Z-rpZtswCzFJ2ZwK@google.com> (raw)
In-Reply-To: <20250331150550.510320-1-pbonzini@redhat.com>
On Mon, Mar 31, 2025, Paolo Bonzini wrote:
> TSC_DEADLINE is now advertised unconditionally by KVM_GET_SUPPORTED_CPUID,
> since commit 9be4ec35d668 ("KVM: x86: Advertise TSC_DEADLINE_TIMER in
> KVM_GET_SUPPORTED_CPUID", 2024-12-18). Adjust the documentation to
> reflect the new behavior.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
Sorry, at one point I even had this on my todo list for that series.
Reviewed-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2025-03-31 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:05 [PATCH] Documentation: KVM: KVM_GET_SUPPORTED_CPUID now exposes TSC_DEADLINE Paolo Bonzini
2025-03-31 19:13 ` Sean Christopherson [this message]
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=Z-rpZtswCzFJ2ZwK@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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