From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [Qemu-devel] Re: KVM call agenda for Feb 9 Date: Tue, 09 Feb 2010 09:52:25 +0100 Message-ID: <4B712249.4020703@web.de> References: <20100209012851.GJ25751@x200.localdomain> <4B710714.1020109@redhat.com> <02FDE8B6-CCC9-4EA5-B7EB-6EFC6497C268@suse.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC994524602DDFC05AC528849" Cc: Avi Kivity , Chris Wright , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:53698 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751334Ab0BIIw1 (ORCPT ); Tue, 9 Feb 2010 03:52:27 -0500 In-Reply-To: <02FDE8B6-CCC9-4EA5-B7EB-6EFC6497C268@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC994524602DDFC05AC528849 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Alexander Graf wrote: > On 09.02.2010, at 07:56, Avi Kivity wrote: >> - rcuify/fine-grain qemu locks >=20 > And this should be done either way, but is probably not a short-term go= al. >=20 Indeed. We won't get around this longterm as it is a scalability bottleneck and a killer for RT guest load. We can't push everything into the kernel. Qemu needs a smart plan how to gradually convert its CPU and device model to fine-grained locking. Jan --------------enigC994524602DDFC05AC528849 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAktxIkkACgkQitSsb3rl5xQGJACgowlRx8AR24nVi2D+gAHVEMQS idcAnjh9SGXEzlwg3/pa9oz4hhas97qo =7Vj0 -----END PGP SIGNATURE----- --------------enigC994524602DDFC05AC528849--