Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754970AbcDATV7 (ORCPT ); Fri, 1 Apr 2016 15:21:59 -0400 Received: from mail-lb0-f196.google.com ([209.85.217.196]:32830 "EHLO mail-lb0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751210AbcDATVy (ORCPT ); Fri, 1 Apr 2016 15:21:54 -0400 MIME-Version: 1.0 In-Reply-To: <1459525755-36968-2-git-send-email-shannon.zhao@linaro.org> References: <1459525755-36968-1-git-send-email-shannon.zhao@linaro.org> <1459525755-36968-2-git-send-email-shannon.zhao@linaro.org> Date: Fri, 1 Apr 2016 21:21:52 +0200 X-Google-Sender-Auth: pxNYeQ6T7FT6VV3MwhIIPklT5XE Message-ID: Subject: Re: [PATCH v10 01/17] Xen: ACPI: Hide UART used by Xen From: "Rafael J. Wysocki" To: Shannon Zhao Cc: "linux-arm-kernel@lists.infradead.org" , stefano.stabellini@citrix.com, david.vrabel@citrix.com, "devicetree@vger.kernel.org" , linux-efi@vger.kernel.org, Linux Kernel Mailing List , Catalin Marinas , Will Deacon , julien.grall@arm.com, peter.huangpeng@huawei.com, xen-devel@lists.xen.org, Shannon Zhao , "Rafael J. Wysocki" , Len Brown , "open list:ACPI" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2711 Lines: 77 On Fri, Apr 1, 2016 at 5:48 PM, Shannon Zhao wrote: > ACPI 6.0 introduces a new table STAO to list the devices which are used > by Xen and can't be used by Dom0. On Xen virtual platforms, the physical > UART is used by Xen. So here it hides UART from Dom0. > > CC: "Rafael J. Wysocki" (supporter:ACPI) > CC: Len Brown (supporter:ACPI) > CC: linux-acpi@vger.kernel.org (open list:ACPI) > Signed-off-by: Shannon Zhao > --- > drivers/acpi/scan.c | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 71 insertions(+) > > diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c > index 5f28cf7..4d2d9eb 100644 > --- a/drivers/acpi/scan.c > +++ b/drivers/acpi/scan.c > @@ -45,6 +45,7 @@ static LIST_HEAD(acpi_scan_handlers_list); > DEFINE_MUTEX(acpi_device_lock); > LIST_HEAD(acpi_wakeup_device_list); > static DEFINE_MUTEX(acpi_hp_context_lock); A comment here would be useful explaining that the below is an exceptional thing an nothing like it is expected to be needed if foreseeable future. > +static u64 spcr_uart_addr; > > struct acpi_dep_data { > struct list_head node; > @@ -1453,6 +1454,44 @@ static int acpi_add_single_object(struct acpi_device **child, > return 0; > } > > +static acpi_status acpi_get_resource_memory(struct acpi_resource *ares, > + void *context) > +{ > + struct resource *res = context; > + > + if (acpi_dev_resource_memory(ares, res)) > + return AE_CTRL_TERMINATE; > + > + return AE_OK; > +} > + > +static bool acpi_device_should_be_hidden(acpi_handle handle) > +{ > + acpi_status status; > + struct resource res; > + > + /* Check if it should ignore the UART device */ > + if (!(spcr_uart_addr && acpi_has_method(handle, METHOD_NAME__CRS))) > + return false; > + > + /* > + * The UART device described in SPCR table is assumed to have only one > + * memory resource present. So we only look for the first one here. > + */ > + status = acpi_walk_resources(handle, METHOD_NAME__CRS, > + acpi_get_resource_memory, &res); > + if (ACPI_FAILURE(status)) > + return false; > + > + if (res.start == spcr_uart_addr) { What about restructuring that a bit. if (ACPI_FAILURE(status) || res.start != spcr_uart_addr) return false; > + printk(KERN_INFO PREFIX "The UART device @%pa in SPCR table will be hidden\n", > + &res.start); And maybe use acpi_handle_info() for this message? Thanks, Rafael