Received: by 10.223.176.46 with SMTP id f43csp764594wra; Fri, 19 Jan 2018 01:23:23 -0800 (PST) X-Google-Smtp-Source: ACJfBouymv9iouk/n3gNua1lRnFQyjrU8IcBftDWJ2cQiDZTySWiI0EtGKt5lrXM6G69kx8gCciy X-Received: by 10.99.60.88 with SMTP id i24mr24594340pgn.1.1516353803026; Fri, 19 Jan 2018 01:23:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516353802; cv=none; d=google.com; s=arc-20160816; b=kR/RC2Q0bo/z17bmiWRcDMUVmBzlzKY9C+ffht27dGcTcUMgBeb683NDWit5dBbOHq YGVkXRqmViP4AEk6nO9oPDewfvhFgcoyvFepkG/kHxrFd1Sp8KrCMpqgfaQXjHL2tjXU bWgg0fD9urHVAaJLRmwnfLKJTESmxdauL/x2m9S/FggWhDd9Vkn/OyrIAQtQ31ChqgF2 JfQazXSvOqsFTFOCpDM9pUTr9PbUyntaLDiv6PPaqqbTTnO6uPgYMvKvjZUCdcQ32P0L Xp71kz4DXj0iz70a0Qqb0O9KDCFSVCKvpEu5pg9ZSbzMorAllVEZONp/vU588kMi8zmm 4spA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=a61IF3ehkRmJrRsOLKhvpS6gJnlWaJF7eYRy3BPXtVk=; b=Ymx7DOMVwVsObJlmEpbeHCvgONABTew2gHs4p9FuYIYhYzcl3WDq9IpIsMKvRo4e5s wVPZO7vnpth/ZxMSymbJ+UU6TuKtWmRUevlS5qiOU5/Gx4trkBAIIuLVT9iYkPPgTSGd b3HM202pIX+Pndq6Uclg5vkrGhaLOnOk8LNanqdABFP+jK9WgM7CTZ1f3fqGa7fBypht v1SNLSCmFqo6/Tmb7aK3dn60lnyUidrtB+TMJvFg1TGyifrKTy1oC/yIi6lwEjoWQDgz RsO93CTZ4emcmhX/xT7Yj+QkslqwyP84lGVCQF/mGhs9wx/g48DJmfgLFnjoXYDNkCK7 oEYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t24si4662882pfe.136.2018.01.19.01.23.09; Fri, 19 Jan 2018 01:23:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755257AbeASJWb (ORCPT + 99 others); Fri, 19 Jan 2018 04:22:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54964 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750841AbeASJW1 (ORCPT ); Fri, 19 Jan 2018 04:22:27 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F21762DE4B; Fri, 19 Jan 2018 09:22:26 +0000 (UTC) Received: from localhost (ovpn-8-21.pek2.redhat.com [10.72.8.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 567416199B; Fri, 19 Jan 2018 09:22:26 +0000 (UTC) Date: Fri, 19 Jan 2018 17:22:23 +0800 From: Baoquan He To: Dou Liyang Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com, x86@kernel.org, rostedt@goodmis.org, jgross@suse.com, peterz@infradead.org, uobergfe@redhat.com, joro@8bytes.org Subject: Re: [RESEND PATCH 3/3] x86/apic: Clean up the names of legacy irq mode setting related functions Message-ID: <20180119092223.GH1753@localhost.localdomain> References: <1515123732-28908-1-git-send-email-bhe@redhat.com> <20180105043929.GL7235@x1> <20180119072130.GG1753@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 19 Jan 2018 09:22:27 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/19/18 at 04:06pm, Dou Liyang wrote: > > > At 01/19/2018 03:21 PM, Baoquan He wrote: > > On 01/19/18 at 02:42pm, Dou Liyang wrote: > > > Hi Baoquan, > > > > > > At 01/05/2018 12:39 PM, Baoquan He wrote: > > > [...] > > > > /* > > > > - * Not an __init, needed by kexec/kdump code. > > > > - * For safety IO-APIC and Local APIC need be cleared before this. > > > > + * In legacy irq mode, full DOS compatibility with the uniprocessor PC/AT is > > > > + * provided by using the APICs in conjunction with standard 8259A-equivalent > > > > + * programmable interrupt controllers (PICs). It's necessary to deliver legacy > > > > + * interrupts even when APIC mode is not enabled. This is required by kexec/ > > > > + * kdump before enter into the 2nd kernel. > > > > */ > > > > void switch_to_legacy_irq_mode(void) > > > > { > > > > if (!nr_legacy_irqs()) > > > > return; > > > > - x86_io_apic_ops.disable(); > > > > + ioapic_set_virtual_wire_mode(); > > > > + > > > > + if (boot_cpu_has(X86_FEATURE_APIC) || apic_from_smp_config()) > > > > + lapic_set_legacy_irq_mode(ioapic_i8259.pin != -1); > > > > > > Seems these two function, ioapic/lapic_set_legacy_irq_mode should be > > > exclusive. > > > > Thanks for looking into this, dou! > > > > It might be not exclusive. You can see mp_spec 3.6.2.2 Virtual Wire Mode > > Oops! Sorry to confuse you, here what I want to say is that the code > make me think that we set through IO-APIC first, then set through > Local-APIC then. But, we can be only in one mode of them. > > Just worry about this code seems ignore the irq remapping situation. > > We call switch_to_legacy_irq_mode() directly in machine_kexec(), > why we also set x86_io_apic_ops: > > .disable = switch_to_legacy_irq_mode You are right, this is not very clear. Since we call switch_to_legacy_irq_mode() directly, nobody will call x86_io_apic_ops.disable() any more. Should keep native_disable_io_apic() and let x86_io_apic_ops.disable() to point at it. Thanks Baoquan > > > subsection, there are two kinds of virtual wire mode, one is > > 8259A-Equivalent pics is connected to lint0 of boot cpu LAPIC, the other > > is 8259A-Equivalent pics go through IO-APIC, then is connected to lint0 > > of LAPIC. Whatever it is, LAPIC need be set as through-lapic. > > > > Yes, Absolutely right! > > > Above is what I got from mp_spec. But from function > > native_disable_io_apic() and disconnect_bsp_APIC(), the code seems to be > > telling that if io-apic is connected to 8259A-Equivalent pics, we need > > mask lvt0 of LAPIC. This conflicts with mp_spec 3.6.2.2. > > > > I think so. > > Thanks, > dou. > > Thanks > > Baoquan > > > > > > But We do that because both the through-lapic and through-ioapic virtual > > > wire mode need setup the APIC_SPIV_APIC_ENABLED which is only located in > > > the lapic_set_legacy_irq_mode(). So we need call them both. > > > > > > IMO, this cleanup may not make it clear. we can separate these two mode > > > totally or just keep it like before. > > > > > > Thanks, > > > dou. > > > > } > > > > #ifdef CONFIG_X86_32 > > > > diff --git a/arch/x86/kernel/x86_init.c b/arch/x86/kernel/x86_init.c > > > > index 1151ccd72ce9..c30f0f273dbd 100644 > > > > --- a/arch/x86/kernel/x86_init.c > > > > +++ b/arch/x86/kernel/x86_init.c > > > > @@ -148,5 +148,5 @@ void arch_restore_msi_irqs(struct pci_dev *dev) > > > > struct x86_io_apic_ops x86_io_apic_ops __ro_after_init = { > > > > .read = native_io_apic_read, > > > > - .disable = native_disable_io_apic, > > > > + .disable = switch_to_legacy_irq_mode, > > > > }; > > > > diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c > > > > index 49721b4e1975..751472ddf536 100644 > > > > --- a/drivers/iommu/irq_remapping.c > > > > +++ b/drivers/iommu/irq_remapping.c > > > > @@ -37,7 +37,7 @@ static void irq_remapping_disable_io_apic(void) > > > > * now. > > > > */ > > > > if (boot_cpu_has(X86_FEATURE_APIC) || apic_from_smp_config()) > > > > - disconnect_bsp_APIC(0); > > > > + lapic_set_legacy_irq_mode(0); > > > > } > > > > static void __init irq_remapping_modify_x86_ops(void) > > > > > > > > > > > > > > > > > >