public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH v4 5/7] KVM: Recalculate destination vcpu map
Date: Thu, 21 Mar 2013 07:34:22 +0200	[thread overview]
Message-ID: <20130321053422.GE9382@redhat.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E099E9905@SHSMSX101.ccr.corp.intel.com>

On Thu, Mar 21, 2013 at 05:30:32AM +0000, Zhang, Yang Z wrote:
> Gleb Natapov wrote on 2013-03-21:
> > On Thu, Mar 21, 2013 at 03:42:46AM +0000, Zhang, Yang Z wrote:
> >> Gleb Natapov wrote on 2013-03-20:
> >>> On Wed, Mar 20, 2013 at 07:36:17PM +0800, Yang Zhang wrote:
> >>>> From: Yang Zhang <yang.z.zhang@Intel.com>
> >>>> 
> >>>> Update RTC interrrupt's destination vcpu map when ioapic entry of RTC
> >>>> or apic register (id, ldr, dfr) is changed.
> >>>> 
> >>>> Signed-off-by: Yang Zhang <yang.z.zhang@Intel.com>
> >>>> ---
> >>>>  virt/kvm/ioapic.c |    9 +++++++--
> >>>>  1 files changed, 7 insertions(+), 2 deletions(-)
> >>>> diff --git a/virt/kvm/ioapic.c b/virt/kvm/ioapic.c
> >>>> index ddf9414..91b4c08 100644
> >>>> --- a/virt/kvm/ioapic.c
> >>>> +++ b/virt/kvm/ioapic.c
> >>>> @@ -121,6 +121,7 @@ void kvm_ioapic_scan_entry(struct kvm_vcpu *vcpu,
> >>>>  { 	struct kvm_ioapic *ioapic = vcpu->kvm->arch.vioapic; 	union
> >>>>  kvm_ioapic_redirect_entry *e; +	unsigned long *rtc_map =
> >>>>  ioapic->rtc_status.vcpu_map; 	struct kvm_lapic_irq irqe; 	int index;
> >>>> @@ -130,15 +131,19 @@ void kvm_ioapic_scan_entry(struct kvm_vcpu
> > *vcpu,
> >>>>  		if (!e->fields.mask &&
> >>>>  			(e->fields.trig_mode == IOAPIC_LEVEL_TRIG ||
> >>>>  			 kvm_irq_has_notifier(ioapic->kvm, KVM_IRQCHIP_IOAPIC,
> >>>> -				 index))) {
> >>>> +				 index) || index == 8)) {
> >>>>  			irqe.dest_id = e->fields.dest_id;
> >>>>  			irqe.vector = e->fields.vector;
> >>>>  			irqe.dest_mode = e->fields.dest_mode;
> >>>>  			irqe.shorthand = 0;
> >>>>  
> >>>>  			if (kvm_apic_match_dest(vcpu, NULL, irqe.shorthand,
> >>>> -						irqe.dest_id, irqe.dest_mode))
> >>>> +						irqe.dest_id, irqe.dest_mode)) {
> >>>>  				__set_bit(irqe.vector, eoi_exit_bitmap);
> >>>> +				if (index == 8)
> >>>> +					__set_bit(vcpu->vcpu_id, rtc_map);
> >>>> +			} else if (index == 8)
> >>>> +				__clear_bit(vcpu->vcpu_id, rtc_map);
> >>> rtc_map bitmap is accessed from different vcpus simultaneously so access
> >>> has to be atomic. We also have a race:
> >>> 
> >>> vcpu0                               iothread
> >>> ioapic config changes
> >>> request scan ioapic
> >>>                                      inject rtc interrupt
> >>>                                      use old vcpu mask
> >>> scan_ioapic()
> >>> recalculate vcpu mask
> >>> 
> >>> So this approach (suggested by me :() will not work.
> >>> 
> >>> Need to think about it some more. May be your idea of building a bitmap
> >>> while injecting the interrupt is the way to go indeed: pass a pointer to
> >>> a bitmap to kvm_irq_delivery_to_apic() and build it there. Pass NULL
> >>> pointer if caller does not need to track vcpus.
> >> Or, we can block inject rtc interrupt during recalculate vcpu map.
> >> 
> >> if(need_eoi > 0 && in_recalculating)
> >> return coalesced
> >> 
> > This should be ||. Then you need to maintain in_recalculating and
> > recalculations requests may overlap. Too complex and fragile.
> It should not be too complex. How about the following logic?
> 
> when make scan ioapic request:
> kvm_vcpu_scan_ioapic()
> {
> kvm_for_each_vcpu()
> 	in_recalculating++;
> }
> 
> Then on each vcpu's request handler:
> vcpu_scan_ioapic()
> {
> in_recalculating--;
> }
> 
kvm_vcpu_scan_ioapic() can be called more often then vcpu_scan_ioapic()

> And when delivering RTC interrupt:
> if(need_eoi > 0 || in_recalculating)
> 	return coalesced
> 
> 
> > 
> > --
> > 			Gleb.
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> Best regards,
> Yang
> 

--
			Gleb.

  reply	other threads:[~2013-03-21  5:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 11:36 [PATCH v4 0/7] Use eoi to track RTC interrupt delivery status Yang Zhang
2013-03-20 11:36 ` [PATCH v4 1/7] KVM: Call kvm_apic_match_dest() to check destination vcpu Yang Zhang
2013-03-20 12:16   ` Gleb Natapov
2013-03-20 11:36 ` [PATCH v4 2/7] KVM: Call common update function when ioapic entry changed Yang Zhang
2013-03-20 11:36 ` [PATCH v4 3/7] KVM: Add vcpu info to ioapic_update_eoi() Yang Zhang
2013-03-20 11:36 ` [PATCH v4 4/7] KVM: Introduce struct rtc_status Yang Zhang
2013-03-20 11:36 ` [PATCH v4 5/7] KVM: Recalculate destination vcpu map Yang Zhang
2013-03-20 15:22   ` Gleb Natapov
2013-03-21  3:42     ` Zhang, Yang Z
2013-03-21  5:08       ` Gleb Natapov
2013-03-21  5:30         ` Zhang, Yang Z
2013-03-21  5:34           ` Gleb Natapov [this message]
2013-03-21  5:39             ` Zhang, Yang Z
2013-03-21  6:57               ` Gleb Natapov
2013-03-21  7:01                 ` Zhang, Yang Z
2013-03-21  7:02     ` Zhang, Yang Z
2013-03-21  7:04       ` Gleb Natapov
2013-03-20 11:36 ` [PATCH v4 6/7] KVM: Add reset/restore rtc_status support Yang Zhang
2013-03-20 11:36 ` [PATCH v4 7/7] KVM: Use eoi to track RTC interrupt delivery status Yang Zhang

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=20130321053422.GE9382@redhat.com \
    --to=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=xiantao.zhang@intel.com \
    --cc=yang.z.zhang@intel.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