From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
stefano.stabellini@citrix.com, david.vrabel@citrix.com,
catalin.marinas@arm.com, will.deacon@arm.com,
xen-devel@lists.xen.org, devicetree@vger.kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
shannon.zhao@linaro.org, peter.huangpeng@huawei.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v8 01/17] Xen: ACPI: Hide UART used by Xen
Date: Tue, 29 Mar 2016 16:00:26 +0800 [thread overview]
Message-ID: <56FA361A.6080104@huawei.com> (raw)
In-Reply-To: <20160325171547.GB29822@localhost>
On 2016/3/26 1:15, Bjorn Helgaas wrote:
> On Fri, Mar 25, 2016 at 04:05:49PM +0800, Shannon Zhao wrote:
>> > From: Shannon Zhao <shannon.zhao@linaro.org>
>> >
>> > 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" <rjw@rjwysocki.net> (supporter:ACPI)
>> > CC: Len Brown <lenb@kernel.org> (supporter:ACPI)
>> > CC: linux-acpi@vger.kernel.org (open list:ACPI)
>> > Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>> > ---
>> > drivers/acpi/scan.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>> > 1 file changed, 68 insertions(+)
>> >
>> > diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
>> > index 5f28cf7..5420cc5 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);
>> > +static u64 spcr_uart_addr;
>> >
>> > struct acpi_dep_data {
>> > struct list_head node;
>> > @@ -1453,6 +1454,41 @@ 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 != 0) {
>> > + if (!acpi_has_method(handle, METHOD_NAME__CRS))
>> > + return false;
>> > +
>> > + 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) {
>> > + printk(KERN_INFO PREFIX "The UART device in SPCR table will be hidden\n");
> Can we at least print out the ACPI device path and address here for
> debugging purposes? IMHO, kernel messages that contain only static
> text are always dubious. There's almost always a useful address, IRQ,
> return value, etc., that could be included.
>
Ok, I'll add the device address in the message and update this patch.
Thanks,
--
Shannon
next prev parent reply other threads:[~2016-03-29 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1458830676-27075-1-git-send-email-shannon.zhao@linaro.org>
2016-03-24 14:44 ` [PATCH v7 01/17] Xen: ACPI: Hide UART used by Xen Shannon Zhao
2016-03-24 15:08 ` Rafael J. Wysocki
2016-03-25 7:38 ` Shannon Zhao
[not found] ` <1458830676-27075-2-git-send-email-shannon.zhao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-03-25 8:05 ` [PATCH v8 " Shannon Zhao
2016-03-25 17:00 ` Rafael J. Wysocki
[not found] ` <7418231.W9aSFKr1zs-sKB8Sp2ER+y1GS7QM15AGw@public.gmane.org>
2016-03-26 13:14 ` Stefano Stabellini
2016-03-25 17:15 ` Bjorn Helgaas
2016-03-26 12:44 ` Stefano Stabellini
2016-03-29 8:00 ` Shannon Zhao [this message]
2016-03-29 8:08 ` [RESEND PATCH v9 " Shannon Zhao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56FA361A.6080104@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=david.vrabel@citrix.com \
--cc=devicetree@vger.kernel.org \
--cc=helgaas@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.huangpeng@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=shannon.zhao@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox