From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH stub] kvm: caching API for interrupts Date: Sun, 29 Jul 2012 22:03:45 +0200 Message-ID: <50159721.4000909@redhat.com> References: <20120729200058.GA13557@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: avi@redhat.com, kvm@vger.kernel.org To: "Michael S. Tsirkin" Return-path: Received: from mail-wi0-f170.google.com ([209.85.212.170]:55434 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753359Ab2G2UDu (ORCPT ); Sun, 29 Jul 2012 16:03:50 -0400 Received: by wibhq12 with SMTP id hq12so1933005wib.1 for ; Sun, 29 Jul 2012 13:03:49 -0700 (PDT) In-Reply-To: <20120729200058.GA13557@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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