From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752433Ab0JENLe (ORCPT ); Tue, 5 Oct 2010 09:11:34 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:37538 "EHLO SMTP.EU.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752222Ab0JENLd (ORCPT ); Tue, 5 Oct 2010 09:11:33 -0400 X-IronPort-AV: E=Sophos;i="4.57,284,1283731200"; d="scan'208";a="2194636" Date: Tue, 5 Oct 2010 14:11:42 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball-desktop To: Konrad Rzeszutek Wilk CC: Stefano Stabellini , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xensource.com" , Jeremy Fitzhardinge Subject: Re: [Xen-devel] [PATCH v2 01/10] xen: remap GSIs as pirqs when running as initial domain In-Reply-To: <20101004192426.GA10291@dumpdata.com> Message-ID: References: <1286191730-3188-1-git-send-email-stefano.stabellini@eu.citrix.com> <20101004192426.GA10291@dumpdata.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 Oct 2010, Konrad Rzeszutek Wilk wrote: > > + gsi = xen_register_gsi(gsi, trigger, polarity); > > What happend here? Tabs-gone-wild? Oops, I'll fix that. > > + /* > > + * stash over-ride to indicate we've been here > > + * and for later update of acpi_gbl_FADT > > + */ > > I think that comment is obsolete. We are not stashing anything? Yes, it is obsolete. I'll remove it. > > > > int __init pci_xen_init(void) > > { > > - if (!xen_pv_domain() || xen_initial_domain()) > > + if (!xen_pv_domain() || xen_initial_domain()) > > What changed? They look exactly the same? > Another editing error unfortunately. > > +void __init xen_setup_pirqs(void) > > +{ > > + int irq; > > +#ifndef CONFIG_SMP > > + int nr_ioapics = 1; > > +#endif > > Should this be defined in a header instead? Was this nr_ioapics==1 > meant to fall in the '0 == nr_ioapics' to setup the first sixteen > irqs? > > Is CONFIG_X86_IO_APIC more appropiate than CONFIG_SMP? I think it was supposed to fix a compilation error in case CONFIG_X86_IO_APIC is not set, so that in both cases in which an ioapic is not present in the system or the ioapic support is not compiled in the kernel we would fall in the '0 == nr_ioapics' code path. So I guess the right thing to do here would be to replace CONFIG_SMP with CONFIG_X86_IO_APIC. I don't think that it is worth moving these three lines into an header file.