From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] [patch 2/6] Use machine options to emulate -no-kvm-irqchip Date: Wed, 03 Oct 2012 12:16:54 -0500 Message-ID: <878vbn4gs9.fsf@codemonkey.ws> References: <20121003105255.972669952@amt.cnet> <20121003105509.391284251@amt.cnet> <87fw5vhb5a.fsf@codemonkey.ws> <20121003150341.GA15164@amt.cnet> <506C5DED.7000705@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Gerd Hoffmann To: Jan Kiszka , Marcelo Tosatti Return-path: Received: from e23smtp01.au.ibm.com ([202.81.31.143]:33633 "EHLO e23smtp01.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932765Ab2JCRRH (ORCPT ); Wed, 3 Oct 2012 13:17:07 -0400 Received: from /spool/local by e23smtp01.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 4 Oct 2012 03:15:04 +1000 Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay05.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q93H7Jix21823696 for ; Thu, 4 Oct 2012 03:07:19 +1000 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q93HH1AP014693 for ; Thu, 4 Oct 2012 03:17:01 +1000 In-Reply-To: <506C5DED.7000705@web.de> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka writes: > On 2012-10-03 17:03, Marcelo Tosatti wrote: >> On Wed, Oct 03, 2012 at 09:40:17AM -0500, Anthony Liguori wrote: >>> Marcelo Tosatti writes: >>> >>>> Commit 3ad763fcba5bd0ec5a79d4a9b6baeef119dd4a3d from qemu-kvm.git. >>>> >>>> From: Jan Kiszka >>>> >>>> Upstream is moving towards this mechanism, so start using it in qemu-kvm >>>> already to configure the specific defaults: kvm enabled on, just like >>>> in-kernel irqchips. >>>> >>>> Signed-off-by: Marcelo Tosatti >>> >>> >>> Reviewed-by: Anthony Liguori >>> >>> Although it's a little odd to have From: Jan without a SoB... >> >> Agree, Jan can you ACK? > > I wasn't able to join the call yesterday: Is there a removal schedule > associated with those switches? Also, why pushing things upstream, even > when only for one release, that have been loudly deprecated for a while > in qemu-kvm? Some switches are lacking deprecated warnings on the > console, and -no-kvm is missing completely. I tend to focus on patch 1 & > 5, dropping the rest - based on relevance for production use. The distros need to keep these flags to do the switch. I see no point in deprecating them since they're trivially easy to maintain. So we'd just support them forever. Regards, Anthony Liguori > > Jan