From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL (sort of)] KVM: x86: Static call changes for 6.11
Date: Wed, 17 Jul 2024 07:52:40 +0200 [thread overview]
Message-ID: <4b0fd060-7095-46f2-840b-f5d88f94eecf@redhat.com> (raw)
In-Reply-To: <ZpaV7kaVL1rj7MXj@google.com>
On 7/16/24 17:46, Sean Christopherson wrote:
> No, I think you misread the #if-#elif-#else. It's only the !HAVE_STATIC_CALL
> case that requires use of static_call_cond().
Oh, of course - the "select HAVE_STATIC_CALL" is right above the "select
HAVE_STATIC_CALL_INLINE if HAVE_OBJTOOL" line. I was definitely
overthinking it.
Paolo
next prev parent reply other threads:[~2024-07-17 5:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 23:56 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Single Xen fix for 6.10 or 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: Generic changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Remove MTRR virtualization Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: PMU changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: Selftests " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL (sort of)] KVM: x86: Static call " Sean Christopherson
2024-07-16 14:16 ` Paolo Bonzini
2024-07-16 15:46 ` Sean Christopherson
2024-07-17 5:52 ` Paolo Bonzini [this message]
2024-07-12 23:56 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2024-07-12 23:57 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
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=4b0fd060-7095-46f2-840b-f5d88f94eecf@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®