From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: qemu-kvm.git build problem
Date: Mon, 11 Jan 2010 12:18:01 +0200
Message-ID: <4B4AFAD9.3010604@redhat.com>
References: <1262025646.2774.16.camel@localhost.localdomain> <1263014581.2439.207.camel@localhost.localdomain> <4B4AF9D2.3080100@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	KVM mailing list <kvm@vger.kernel.org>,
	Michael Goldish <mgoldish@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Dor Laor <dlaor@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:11379 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752922Ab0AKKSH (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 11 Jan 2010 05:18:07 -0500
In-Reply-To: <4B4AF9D2.3080100@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 01/11/2010 12:13 PM, Jan Kiszka wrote:
>
> BTW, does anybody know how to back-port synchronize_srcu_expedited best?
> It looked like a simple mapping to synchronize_srcu was not sufficient
> to achieve the same performance as with the pre-srcu locking (e.g.
> guest&host stalled during guest's framebuffer setup).
>    

Isn't it sufficient to backport kernel/srcu.c?  I thought no sched.c 
changes were necessary.

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