From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v3 1/4] KVM: x86: Split the APIC from the rest of
 IRQCHIP.
Date: Fri, 5 Jun 2015 03:19:34 -0400 (EDT)
Message-ID: <2129177540.15767728.1433488774623.JavaMail.zimbra@redhat.com>
References: <1433289107-20638-1-git-send-email-srutherford@google.com> <556EC0D1.8050506@redhat.com> <20150604203820.GA28041@google.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Steve Rutherford <srutherford@google.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx6-phx2.redhat.com ([209.132.183.39]:33564 "EHLO
	mx6-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751074AbbFEHTh (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 5 Jun 2015 03:19:37 -0400
In-Reply-To: <20150604203820.GA28041@google.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>


> From the perspective of avoiding impacting other architectures, this is a
> good idea, but the naming seems strange in the x86 case. Having
> irqchip_in_kernel be "true" when the ioapic/pic are in userspace seems
> strange. Admittedly, the irqchip isn't a "real" concept on x86, so
> inventing a new meaning is fine.

>>From the KVM point of view, the "irqchip" is whatever delivers
interrupts to the vCPU---which is the LAPIC for x86.

Paolo