From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=40750 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OgWyO-0005D0-5c for qemu-devel@nongnu.org; Wed, 04 Aug 2010 01:57:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OgWyM-00014x-UH for qemu-devel@nongnu.org; Wed, 04 Aug 2010 01:57:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57183) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OgWyM-00014o-Nb for qemu-devel@nongnu.org; Wed, 04 Aug 2010 01:57:02 -0400 Message-ID: <4C590128.9030602@redhat.com> Date: Wed, 04 Aug 2010 08:56:56 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35? References: <4C5847CD.9080107@codemonkey.ws> <4C5848C7.3090806@redhat.com> <4C584982.5000108@codemonkey.ws> <4C584B66.5070404@redhat.com> <4C5854F1.3000905@codemonkey.ws> <4C5858B2.9090801@redhat.com> <4C585F5B.5070502@codemonkey.ws> <4C58635B.7020407@redhat.com> <20100803191346.GA28523@amd.home.annexia.org> <4C586C6E.9030002@redhat.com> <20100803200057.GB28523@amd.home.annexia.org> <4C5880BC.2080802@codemonkey.ws> In-Reply-To: <4C5880BC.2080802@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: kvm@vger.kernel.org, "Richard W.M. Jones" , Gleb Natapov , qemu-devel@nongnu.org On 08/03/2010 11:49 PM, Anthony Liguori wrote: > >> We could demand that OSes write device drivers for more qemu devices >> -- already OS vendors write thousands of device drivers for all sorts >> of obscure devices, so this isn't really much of a demand for them. >> In fact, they're already doing it. > > So far, MS hasn't quite gotten the clue yet that they should write > device drivers for qemu :-) To be fair, we haven't actually demanded that they do. > In fact, noone has. Strangely, the reverse has happened - I think virtualbox has written virtio device models for their VMM. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.