Re: [PATCH stub] kvm: caching API for interrupts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jul 29, 2012 at 10:03:45PM +0200, Paolo Bonzini wrote:
> Il 29/07/2012 22:00, Michael S. Tsirkin ha scritto:
> > I've been looking at adding caching for IRQs so that we don't need to
> > scan all VCPUs on each interrupt.  One issue I had a problem with, is
> > how the cache structure can be used from both a thread (to fill out the
> > cache) and interrupt (to actually send if cache is valid).
> > 
> > For now just added a lock field in the cache so we don't need to worry
> > about this, and with such a lock in place we don't have to worry about
> > RCU as cache can be invalidated simply under this lock.
> 
> seqlock?
> 
> Paolo

AFAIK seqlock only works if uses of stale data have no side-effects,
this is not the case here. We could use an rwlock I think.

-- 
MST
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux