From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [RFC Part2 v1 00/21] Enable hierarchy irqdomian on x86 platforms Date: Wed, 24 Sep 2014 21:25:16 +0200 (CEST) Message-ID: References: <1410444228-3134-1-git-send-email-jiang.liu@linux.intel.com> <542279D0.1040603@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <542279D0.1040603@jp.fujitsu.com> Sender: linux-kernel-owner@vger.kernel.org To: Yasuaki Ishimatsu Cc: Jiang Liu , Benjamin Herrenschmidt , Ingo Molnar , "H. Peter Anvin" , "Rafael J. Wysocki" , Bjorn Helgaas , Randy Dunlap , Yinghai Lu , Borislav Petkov , Grant Likely , Marc Zyngier , Konrad Rzeszutek Wilk , Andrew Morton , Tony Luck , Joerg Roedel , Greg Kroah-Hartman , x86@kernel.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-acpi@vger.kernel.org On Wed, 24 Sep 2014, Yasuaki Ishimatsu wrote: > I cannot imagine why the feature makes x86 irq architecture much more clear > and more easy to maintain in this description. Of course, I have read the > following threads: > > https://lkml.org/lkml/2014/9/11/101 Here is the long version of the idea: https://lkml.org/lkml/2014/8/26/707 Short version is: Separate the irq handling entities in a clear layered way instead of having vector/[io]apic specific knowledge/data in places like msi, remap etc. Thanks, tglx