From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 04/19] qemu-kvm: x86: Drop MSR reset
Date: Thu, 5 May 2011 15:23:56 +0300
Message-ID: <20110505122356.GA29181@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>
 <4DC290E3.7000507@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:9294 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751426Ab1EEMYA (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 5 May 2011 08:24:00 -0400
Content-Disposition: inline
In-Reply-To: <4DC290E3.7000507@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Thu, May 05, 2011 at 02:58:27PM +0300, Avi Kivity wrote:
> 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.
> 
s/always/for quite a while/. Unfortunately yes. Unless we put qemu in the kernel
tree and will release them in lock steps of course :)

--
			Gleb.