From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH 5/5] ioeventfd: Introduce KVM_IOEVENTFD_FLAG_SOCKET Date: Thu, 14 Jul 2011 11:07:14 +0300 Message-ID: <1310630834.21171.3.camel@lappy> References: <1309927078-5983-1-git-send-email-levinsasha928@gmail.com> <1309927078-5983-5-git-send-email-levinsasha928@gmail.com> <20110706114203.GA18368@redhat.com> <1309964506.15123.13.camel@sasha> <20110706155135.GA21638@redhat.com> <1310276083.2393.6.camel@sasha> <20110710080559.GC1630@redhat.com> <1310469824.2393.22.camel@sasha> <4E1C2F59.90600@redhat.com> <4E1D442E.6090308@redhat.com> <4E1D9623.70801@redhat.com> <4E1D9E75.1070901@redhat.com> <4E1E9A3B.7090200@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Avi Kivity , "Michael S. Tsirkin" , kvm@vger.kernel.org, Ingo Molnar , Marcelo Tosatti To: Pekka Enberg Return-path: Received: from mail-fx0-f52.google.com ([209.85.161.52]:37379 "EHLO mail-fx0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753715Ab1GNIHb (ORCPT ); Thu, 14 Jul 2011 04:07:31 -0400 Received: by fxd18 with SMTP id 18so725225fxd.11 for ; Thu, 14 Jul 2011 01:07:30 -0700 (PDT) In-Reply-To: <4E1E9A3B.7090200@kernel.org> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2011-07-14 at 10:26 +0300, Pekka Enberg wrote: > On 07/13/2011 04:00 PM, Pekka Enberg wrote: > >> On Wed, Jul 13, 2011 at 3:57 PM, Avi Kivity wrote: > >> >> We'd like to keep 8250 emulation because it's the most robust method > >> >> for getting data out of the kernel when there's problems. It's also > >> >> compatible with earlyprintk and such. > >> > > >> > What do you hope to gain from the optimization? 100ms less boot time? > >> > >> Hmm? I use serial console for logging into the guest and actually > >> using it all the time. > > On 7/13/11 4:32 PM, Avi Kivity wrote: > > Just how fast do you type? > > > > It's not enough to make something faster, it has to be slow to being > > with. The interface is good, but use it where it helps. > > I don't know why you bring up serial console input here. Sasha's > original KVM_IOEVENTFD_FLAG_PIPE patch clearly stated: > > A simple example for practical use is the serial port. we are not > interested in an exit every time a char is written to the port, but > we do need to know what was written so we could handle it on the > guest. > > So it's talking about the serial console output, not input. Yes, I have originally thought of doing the pipefd interface to prevent the overhead caused by console intensive benchmarks on actual benchmarks. It's funny how much slowness spinning the cursor or printing a table incurs. -- Sasha.