From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from claw.goop.org (claw.goop.org [74.207.240.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.goop.org", Issuer "Goop.org CA" (not verified)) by ozlabs.org (Postfix) with ESMTPS id 2317DB7D13 for ; Thu, 11 Mar 2010 05:33:43 +1100 (EST) Message-ID: <4B97E4A7.6060501@goop.org> Date: Wed, 10 Mar 2010 10:27:51 -0800 From: Jeremy Fitzhardinge MIME-Version: 1.0 To: "Eric W. Biederman" Subject: Re: [PATCH] irq: move some interrupt arch_* functions into struct irq_chip. References: <1268218524.11737.68547.camel@zakaz.uk.xensource.com> <1268218559-26784-2-git-send-email-ijc@hellion.org.uk> <86802c441003100406t70dd854fx491f0ee9a6fce62b@mail.gmail.com> <1268225473.11737.69196.camel@zakaz.uk.xensource.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Ian Campbell , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "linuxppc-dev@ozlabs.org" , Ingo Molnar , Paul Mackerras , "H. Peter Anvin" , Thomas Gleixner , Yinghai Lu List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 03/10/2010 09:42 AM, Eric W. Biederman wrote: > All we need between the Xen and the rest of x86 is a convention > so that we never manage the same irqs. At least for domU we are > in an either/or situation so I don't see even that being a problem. > Dom0 too. This is part of the work implementing what we discussed a while back - Xen now completely owns the local and IO apics, so dom0 only deals with Xen, not the hardware. Xen has a completely different interrupt setup path, but at least it isn't a mishmash of Xen stuff and native APIC stuff. J From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932672Ab0CJS16 (ORCPT ); Wed, 10 Mar 2010 13:27:58 -0500 Received: from claw.goop.org ([74.207.240.146]:59260 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932639Ab0CJS1z (ORCPT ); Wed, 10 Mar 2010 13:27:55 -0500 Message-ID: <4B97E4A7.6060501@goop.org> Date: Wed, 10 Mar 2010 10:27:51 -0800 From: Jeremy Fitzhardinge User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.3 MIME-Version: 1.0 To: "Eric W. Biederman" CC: Ian Campbell , Yinghai Lu , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Benjamin Herrenschmidt , Paul Mackerras , "x86@kernel.org" , "linuxppc-dev@ozlabs.org" Subject: Re: [PATCH] irq: move some interrupt arch_* functions into struct irq_chip. References: <1268218524.11737.68547.camel@zakaz.uk.xensource.com> <1268218559-26784-2-git-send-email-ijc@hellion.org.uk> <86802c441003100406t70dd854fx491f0ee9a6fce62b@mail.gmail.com> <1268225473.11737.69196.camel@zakaz.uk.xensource.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/10/2010 09:42 AM, Eric W. Biederman wrote: > All we need between the Xen and the rest of x86 is a convention > so that we never manage the same irqs. At least for domU we are > in an either/or situation so I don't see even that being a problem. > Dom0 too. This is part of the work implementing what we discussed a while back - Xen now completely owns the local and IO apics, so dom0 only deals with Xen, not the hardware. Xen has a completely different interrupt setup path, but at least it isn't a mishmash of Xen stuff and native APIC stuff. J