From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752504Ab1LLLCI (ORCPT ); Mon, 12 Dec 2011 06:02:08 -0500 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:53590 "EHLO pyramind.ukuu.org.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751710Ab1LLLCF (ORCPT ); Mon, 12 Dec 2011 06:02:05 -0500 Date: Mon, 12 Dec 2011 11:02:36 +0000 From: Alan Cox To: Sasha Levin Cc: Thomas Gleixner , Ingo Molnar , Pekka Enberg , LKML Subject: Re: [patch 0/3] kvm tool: Serial emulation overhaul Message-ID: <20111212110236.755eda81@pyramind.ukuu.org.uk> In-Reply-To: <1323687592.16450.0.camel@lappy> References: <20111210132220.083204833@linutronix.de> <20111211103047.GA19299@elte.hu> <20111212102750.469f0d9f@pyramind.ukuu.org.uk> <1323687592.16450.0.camel@lappy> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.8; x86_64-redhat-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWysKsSBQMIAwIZCwj///8wIhxoRDXH9QHCAAABeUlEQVQ4jaXTvW7DIBAAYCQTzz2hdq+rdg494ZmBeE5KYHZjm/d/hJ6NfzBJpp5kRb5PHJwvMPMk2L9As5Y9AmYRBL+HAyJKeOU5aHRhsAAvORQ+UEgAvgddj/lwAXndw2laEDqA4x6KEBhjYRCg9tBFCOuJFxg2OKegbWjbsRTk8PPhKPD7HcRxB7cqhgBRp9Dcqs+B8v4CQvFdqeot3Kov6hBUn0AJitrzY+sgUuiA8i0r7+B3AfqKcN6t8M6HtqQ+AOoELCikgQSbgabKaJW3kn5lBs47JSGDhhLKDUh1UMipwwinMYPTBuIBjEclSaGZUk9hDlTb5sUTYN2SFFQuPe4Gox1X0FZOufjgBiV1Vls7b+GvK3SU4wfmcGo9rPPQzgIabfj4TYQo15k3bTHX9RIw/kniir5YbtJF4jkFG+dsDK1IgE413zAthU/vR2HVMmFUPIHTvF6jWCpFaGw/A3qWgnbxpSm9MSmY5b3pM1gvNc/gQfwBsGwF0VCtxZgAAAAASUVORK5CYII= Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > You can emulate a chip with a 64byte or so FIFO. You can do I/O cycle > > prediction in the kernel part and you can use the empty bit as a clue > > (which is what most serial<->ethernet widgetry does). > > The performance problems here aren't the same performance problems you > have on real hardware. The problem here is that it costs 40k cycles for > the guest to access the emulated chip. How much of that 40K cycles is bouncing back and forth into emulation layers and how much of it is the kernel trap ?