From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932917AbcGICE2 (ORCPT ); Fri, 8 Jul 2016 22:04:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46511 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932486AbcGICE1 (ORCPT ); Fri, 8 Jul 2016 22:04:27 -0400 Date: Sat, 9 Jul 2016 10:04:21 +0800 From: Baoquan He To: Ingo Molnar Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Pavel Machek , linux-acpi@vger.kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Borislav Petkov , Andy Lutomirski , Shaohua Li , Viresh Kumar , Hidehiro Kawai , Juergen Gross , Joerg Roedel , Dave Young , Lv Zheng , Toshi Kani , Mark Salter , Dave Hansen , x86@kernel.org Subject: Re: [PATCH v2 2/2] x86/acpi: Remove the repeated lapic address override entry parsing Message-ID: <20160709020421.GA6185@x1.redhat.com> References: <1467070896-4186-1-git-send-email-bhe@redhat.com> <1467070896-4186-2-git-send-email-bhe@redhat.com> <20160630080118.GD7175@x1.redhat.com> <20160708122755.GA12413@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160708122755.GA12413@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Sat, 09 Jul 2016 02:04:26 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ingo, On 07/08/16 at 02:27pm, Ingo Molnar wrote: > > * Baoquan He wrote: > > > ACPI MADT has a 32-bit field providing lapic address at which > > each processor can access its lapic information. MADT also contains > > an optional entry to provide a 64-bit address to override the 32-bit > > one. However the current code does the lapic address override entry > > parsing twice. One is in early_acpi_boot_init() because AMD NUMA need > > get boot_cpu_id earlier. The other is in acpi_boot_init() which parses > > all MADT entries. > > > > So in this patch remove the repeated code in the 2nd part. Meanwhile > > print lapic override entry information like other MADT entry. > > So this patch is not supposed to change behavior (modulo kernel messages), right? > If so it would make sense to spell that out explicitly in the changelog. I am not sure if I understand your question correctly. In this patch I added the calling of acpi_table_print_madt_entry(header) in acpi_parse_lapic_addr_ovr, it will print information related if a lapic address override entry is provided as below: case ACPI_MADT_TYPE_LOCAL_APIC_OVERRIDE: { struct acpi_madt_local_apic_override *p = (struct acpi_madt_local_apic_override*)header; pr_info("LAPIC_ADDR_OVR (address[%p])\n", (void *)(unsigned long)p->address); } break; This will add one line of message to boot log if lapic addr override entry provided: "LAPIC_ADDR_OVR (address[0xXXXXXXXX])" I don't know if this is the behaviour change (modulo kernel messages) you mentioned. Thanks Baoquan