From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35953) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDYKI-0006Rc-Q7 for qemu-devel@nongnu.org; Tue, 11 Oct 2011 05:08:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDYKG-0003qx-QK for qemu-devel@nongnu.org; Tue, 11 Oct 2011 05:08:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48211) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDYKG-0003qs-I4 for qemu-devel@nongnu.org; Tue, 11 Oct 2011 05:08:40 -0400 Message-ID: <4E940791.1070600@redhat.com> Date: Tue, 11 Oct 2011 11:08:33 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20111010170803.GV9408@redhat.com> <4E933F2D.7090703@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Hack integrating SeaBios / LinuxBoot option rom with QEMU trace backends List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Gleb Natapov , seabios@seabios.org, qemu-devel , "Richard W.M. Jones" On 10/10/2011 09:01 PM, Alexander Graf wrote: > >> For example, one execution of QEMU produced the following log: > >> > >> $ stap qemu-timing.stp > >> 0.000 Start > >> 0.036 Run > >> 0.038 BIOS post > >> 0.180 BIOS int 19 > >> 0.181 BIOS boot OS > >> 0.181 LinuxBoot copy kernel > >> 1.371 LinuxBoot copy initrd > > > > Yeah, there was a thread a bit ago about the performance of the interface to read the kernel/initrd. I think at it was using single byte access instructions and there were patches to use string accessors instead? I can't remember where that threaded ended up. > > IIRC we're already using string accessors, but are still slow. Richard had a nice patch cooked up to basically have the fw_cfg interface be able to DMA its data to the guest. I like the idea. Avi did not. > > And yes, bad -kernel performance does hurt in some workloads. A lot. > > The rep/ins implementation is still slow, optimizing it can help. What does 'perf top' say when running this workload? -- error compiling committee.c: too many arguments to function