mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] KVM: x86: check PIR even for vCPUs with disabled APICv
Date: Thu, 18 Nov 2021 18:56:34 +0100	[thread overview]
Message-ID: <4316fbc5-b758-a7c6-530d-dc5a97f4e97b@redhat.com> (raw)
In-Reply-To: <YZZ8hAjbIJnkkraD@google.com>

On 11/18/21 17:17, Sean Christopherson wrote:
> On Thu, Nov 18, 2021, Paolo Bonzini wrote:
>> On 11/18/21 10:56, Maxim Levitsky wrote:
>>> vmx_sync_pir_to_irr has 'if (KVM_BUG_ON(!vcpu->arch.apicv_active,
>>> vcpu->kvm))' That has to be removed I think for this to work.
>>
>> Good point.
> 
> Hmm, I think I'd prefer to keep it as
> 
> 	if (KVM_BUG_ON(!enable_apicv))
> 		return -EIO;
> 
> since calling it directly or failing to nullify vmx_x86_ops.sync_pir_to_irr when
> APICv is unsupported would lead to all sorts of errors.  It's not a strong
> preference though.
> 

Sure, why not.  There's a few more changes required to handle 
KVM_REQ_EVENT when APICv is !active on the CPU, so I'll post it early 
next week.

(The MOVE/COPY context stuff also exposed itself as a bit of a 
trainwreck and ate half of my day).

Paolo


  reply	other threads:[~2021-11-18 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18  7:25 Paolo Bonzini
2021-11-18  9:56 ` Maxim Levitsky
2021-11-18 11:11   ` Paolo Bonzini
2021-11-18 11:17     ` Maxim Levitsky
2021-11-18 16:17     ` Sean Christopherson
2021-11-18 17:56       ` Paolo Bonzini [this message]
2021-11-18 16:18 ` 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=4316fbc5-b758-a7c6-530d-dc5a97f4e97b@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=seanjc@google.com \
    --cc=stable@vger.kernel.org \
    /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®