From: "Wang,Guangju" <wangguangju@baidu.com>
To: Sean Christopherson <seanjc@google.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jmattson@google.com" <jmattson@google.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"bp@alien8.de" <bp@alien8.de>,
"joro@8bytes.org" <joro@8bytes.org>,
"suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chu,Kaiping" <chukaiping@baidu.com>
Subject: 答复: [PATCH] KVM: x86: Add EOI_INDUCED exit handlers for Hyper-V SynIC vectors
Date: Fri, 8 Jul 2022 01:00:07 +0000 [thread overview]
Message-ID: <4068ff4962154900a6a3535454f4706e@baidu.com> (raw)
In-Reply-To: <YscLvipHbNx+Wy9y@google.com>
> Rather than add a third helper, what about renaming kvm_apic_set_eoi_accelerated() and having the non-accelerated helper call the "acclerated" version? That will document the delta between the non-accelerated patch and the accelerated path.
> The only hiccup is tracing, but that's easy to resolve (or we could just not trace if there's no valid vector to EOI), e.g.
Yeah, rename the function and integrate two paths looks clearer and easier to understand?
Thanks Sean for the suggestion, I will send a new patch with a new subject and changelog.
--
Wang
prev parent reply other threads:[~2022-07-08 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 12:28 [PATCH] KVM: x86: Add EOI_INDUCED exit handlers for Hyper-V SynIC vectors Wang Guangju
2022-07-07 16:37 ` Sean Christopherson
2022-07-08 1:00 ` Wang,Guangju [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=4068ff4962154900a6a3535454f4706e@baidu.com \
--to=wangguangju@baidu.com \
--cc=bp@alien8.de \
--cc=chukaiping@baidu.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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