From: Paolo Bonzini <pbonzini@redhat.com>
To: "Suravee Suthikulpanit" <Suravee.Suthikulpanit@amd.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, joro@8bytes.org
Subject: Re: [PATCH v2 3/3] KVM: SVM: Add irqchip_split() checks before enabling AVIC
Date: Fri, 15 Sep 2017 23:14:23 +0200 [thread overview]
Message-ID: <36af3324-dd87-c932-2b23-4b4ba45047e4@redhat.com> (raw)
In-Reply-To: <dcbe0fce-3d7a-d519-835f-872bf0e65ed2@amd.com>
On 15/09/2017 21:21, Suravee Suthikulpanit wrote:
>>>>
>>>>
>>>> static bool svm_get_enable_apicv(struct kvm_vcpu *vcpu)
>>>> {
>>> A close contender was pr_info_once() here:
>>>
>>> if (avic && !irqchip_split(vcpu->kvm))
>>> pr_info_once(...)
>>>
>>
>> Looks good.
>
> Actually, thinking about it again, this would not work either since
> pr_xxx_once() would only print the message once per loading of kvm_amd
> module. However, we would prefer the message to be printed per VM
> initialization. I also tried adding the check and print this message in
> the kvm_x86_ops.vm_init(), but this also does not work since the
> vm_init() function is called before the
> kvm_vm_ioctl_enable_cap(KVM_CAP_SPLIT_IRQCHIP).
>
> Therefore, pr_info() might be better here, even though this would get
> print per VCPU initialization. Any other suggestions?
My suggestion is to make it pr_info_once. No one looks at dmesg anyway
unless things go very wrong.
Paolo
prev parent reply other threads:[~2017-09-15 21:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 15:42 [PATCH v2 0/3] KVM: SVM: Fix guest not booting w/ AVIC enabled Suravee Suthikulpanit
2017-09-12 15:42 ` [PATCH v2 1/3] KVM: SVM: Refactor AVIC vcpu initialization into avic_init_vcpu() Suravee Suthikulpanit
2017-09-12 15:42 ` [PATCH v2 2/3] KVM: Add struct kvm_vcpu pointer parameter to get_enable_apicv() Suravee Suthikulpanit
2017-09-12 15:42 ` [PATCH v2 3/3] KVM: SVM: Add irqchip_split() checks before enabling AVIC Suravee Suthikulpanit
2017-09-14 15:20 ` Radim Krčmář
2017-09-14 15:23 ` Suravee Suthikulpanit
2017-09-15 19:21 ` Suravee Suthikulpanit
2017-09-15 21:14 ` Paolo Bonzini [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=36af3324-dd87-c932-2b23-4b4ba45047e4@redhat.com \
--to=pbonzini@redhat.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@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
all inboxes | Powered by JetHome®