From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 04/19] qemu-kvm: x86: Drop MSR reset Date: Thu, 05 May 2011 14:58:27 +0300 Message-ID: <4DC290E3.7000507@redhat.com> References: <4DC25AF3.6050704@redhat.com> <4DC25BC5.9090801@siemens.com> <4DC25CDB.9060805@redhat.com> <4DC25F82.2040501@siemens.com> <4DC260DD.5010807@redhat.com> <4DC26388.4090207@siemens.com> <4DC265A5.90301@redhat.com> <4DC26EAA.7080803@siemens.com> <20110505112257.GE19019@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Marcelo Tosatti , "kvm@vger.kernel.org" To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:46692 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159Ab1EEL6c (ORCPT ); Thu, 5 May 2011 07:58:32 -0400 In-Reply-To: <20110505112257.GE19019@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/05/2011 02:22 PM, Gleb Natapov wrote: > > > > We'll see, but I still do not share your concern regarding future > > regressions when removing the fragile reset code. > > > Why do we rely on userspace to properly reset kernel component anyway? > We should introduce cpu/lapic/ioapic/pit/pic resets ASAP. We should, but we'll always have to deal with kernels that don't have reset ioctls. -- error compiling committee.c: too many arguments to function