All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Li, Jiongxi" <jiongxi.li@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/5]KVM:x86, apicv: adjust for virtual interrupt delivery
Date: Wed, 19 Sep 2012 18:19:14 +0300	[thread overview]
Message-ID: <5059E272.3030606@redhat.com> (raw)
In-Reply-To: <D9137FCD9CFF644B965863BCFBEDABB8782E5E@SHSMSX101.ccr.corp.intel.com>

On 09/17/2012 02:28 PM, Li, Jiongxi wrote:
>> > > +	} else if (kvm_apic_vid_enabled(vcpu)) {
>> > > +		if (kvm_cpu_has_interrupt_apic_vid(vcpu) &&
>> > > +		    kvm_x86_ops->interrupt_allowed(vcpu)) {
>> > > +			kvm_queue_interrupt(vcpu,
>> > > +				kvm_cpu_get_interrupt_apic_vid(vcpu), false);
>> > > +			kvm_x86_ops->set_irq(vcpu);
>> > > +		}
>> >
>> > It may be simpler to change kvm_cpu_{has,get}_interrupt to ignore the
>> > apic if virtual interrupt delivery is enabled.
>> OKs
> 
> Kvm_cpu_has_interrupt is also called in other place, no just used to judge whether 
> to inject interrupt manually. For instance, it is called in
kvm_arch_vcpu_runnable.
> In that case, apic can't be ingored. So for safety, I think it is
better to use another
> function here other than change the original kvm_cpu_has_interrupt
function.

Good point.

We can call them *_extint(), since that's what they're accepting.

-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2012-09-19 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05  5:41 [PATCH 2/5]KVM:x86, apicv: adjust for virtual interrupt delivery Li, Jiongxi
2012-09-06 16:22 ` Avi Kivity
2012-09-14 14:15   ` Li, Jiongxi
2012-09-19 14:53     ` Avi Kivity
2012-09-17 11:28   ` Li, Jiongxi
2012-09-19 15:19     ` Avi Kivity [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=5059E272.3030606@redhat.com \
    --to=avi@redhat.com \
    --cc=jiongxi.li@intel.com \
    --cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.