From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: system call time increase when turning on CONFIG_PARAVIRT Date: Fri, 02 Mar 2007 16:16:57 -0800 Message-ID: <45E8BE79.40200@goop.org> References: <1172866274.4898.14.camel@localhost.localdomain> <45E89CFB.4090905@goop.org> <1172877111.8383.4.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1172877111.8383.4.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.osdl.org Errors-To: virtualization-bounces@lists.osdl.org To: tim.c.chen@linux.intel.com Cc: Virtualization Mailing List , linux-kernel@vger.kernel.org List-Id: virtualization@lists.linuxfoundation.org Tim Chen wrote: > I also hope that the performance can be recovered as this option could > enabled in distributions' kernels in future. Yes, the intent is that running a CONFIG_PARAVIRT kernel on native hardware will have negligible performance hit compared to running a non-paravirt kernel. J