Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751628AbdILOW4 (ORCPT ); Tue, 12 Sep 2017 10:22:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38802 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751488AbdILOWw (ORCPT ); Tue, 12 Sep 2017 10:22:52 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com C700080F9F Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=pbonzini@redhat.com Subject: Re: [PATCH 3/3] KVM: SVM: Add irqchip_split() checks before enabling AVIC To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Suravee Suthikulpanit Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, joro@8bytes.org References: <1504669169-4919-1-git-send-email-suravee.suthikulpanit@amd.com> <1504669169-4919-4-git-send-email-suravee.suthikulpanit@amd.com> <20170908155324.GB14748@flask> <9475950b-566f-9425-5de9-9e6677e41043@amd.com> <20170912131727.GA24326@flask> From: Paolo Bonzini Message-ID: <1ab4bded-a6a6-0a10-d3ea-96b7c38b93f0@redhat.com> Date: Tue, 12 Sep 2017 16:22:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170912131727.GA24326@flask> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Tue, 12 Sep 2017 14:22:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 900 Lines: 19 On 12/09/2017 15:17, Radim Krčmář wrote: >>> Yeah, hacking TMR to get the VM exit could result in future bugs. >>> We have to push split irqchip as the deafult in userspaces with this >>> change. >> Actually, I'm not quite sure about the advantages/disadvantages with split >> irqchip, and how it would affect other cases, and why it was not used as >> default currently. > The main advantage of split irqchip is that we're moving code out of the > kernel, and QEMU's irqchip currently has more features too. > > I think it is not the default as the support for split irqchip is recent > (v4.3) and has lower performance, so it is only used in cases that need > the extra features. One other difference is that in-kernel PIT is not supported with split-irqchip, and the QEMU PIT lacks support for reinjecting lost ticks. But this should only be needed for very old guests at this point. Paolo