From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Neqsl-0004lT-AZ
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 09:16:03 -0500
Received: from [199.232.76.173] (port=40117 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Neqsk-0004lF-Ld
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 09:16:02 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <anthony@codemonkey.ws>) id 1Neqsj-0006HX-4b
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 09:16:02 -0500
Received: from mail-iw0-f178.google.com ([209.85.223.178]:47752)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Neqsi-0006HT-TT
	for qemu-devel@nongnu.org; Tue, 09 Feb 2010 09:16:01 -0500
Received: by iwn8 with SMTP id 8so1770167iwn.13
	for <qemu-devel@nongnu.org>; Tue, 09 Feb 2010 06:16:00 -0800 (PST)
Message-ID: <4B716E1D.7000608@codemonkey.ws>
Date: Tue, 09 Feb 2010 08:15:57 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <20100209012851.GJ25751@x200.localdomain>
	<4B710714.1020109@redhat.com>
In-Reply-To: <4B710714.1020109@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: KVM call agenda for Feb 9
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, qemu-devel@nongnu.org, kvm@vger.kernel.org

On 02/09/2010 12:56 AM, Avi Kivity wrote:
> On 02/09/2010 03:28 AM, Chris Wright wrote:
>> Please send in any agenda items you are interested in covering.
>
> hpet overhead on large smp guests
>
> I measured hpet consuming about a half a core's worth of cpu on an 
> idle Windows 2008 R2 64-way guest.  This is mostly due to futex 
> contention, likely from the qemu mutex.
>
> Options:
> - ignore, this is about 1% of the entire system (but overhead might 
> increase greatly if a workload triggers more hpet accesses)
> - push hpet into kernel, with virtio-net, virtio-blk, and kernel-hpet, 
> there's little reason to exit into qemu

Security, shamurity, let's just stick all of qemu in the kernel :-)

> - rcuify/fine-grain qemu locks

Should be pretty straight forward.  It would start with removing the 
locking within kvm*.c such that qemu_mutex isn't acquired until we 
dispatch I/O operations.  Then we can add lockless paths for dispatch as 
we convert device models over.

Regards,

Anthony Liguori