From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932670AbcASIlk (ORCPT ); Tue, 19 Jan 2016 03:41:40 -0500 Received: from szxga01-in.huawei.com ([58.251.152.64]:22860 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752206AbcASIlh (ORCPT ); Tue, 19 Jan 2016 03:41:37 -0500 Message-ID: <569DF6A7.8030709@huawei.com> Date: Tue, 19 Jan 2016 16:41:11 +0800 From: Shannon Zhao User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Stefano Stabellini , Mark Rutland CC: , , , , , , , , , , , , , Ian Campbell Subject: Re: [PATCH v2 11/16] ARM64: ACPI: Check if it runs on Xen to enable or disable ACPI References: <1452840929-19612-1-git-send-email-zhaoshenglong@huawei.com> <1452840929-19612-12-git-send-email-zhaoshenglong@huawei.com> <20160118104142.GC21067@leverpostej> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.16.142] X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.569DF6BB.00C4,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: cba098d06f5dcd630d16e550f4588686 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016/1/18 23:07, Stefano Stabellini wrote: > On Mon, 18 Jan 2016, Mark Rutland wrote: >> > On Fri, Jan 15, 2016 at 02:55:24PM +0800, Shannon Zhao wrote: >>> > > From: Shannon Zhao >>> > > >>> > > When it's a Xen domain0 booting with ACPI, it will supply a /chosen and >>> > > a /hypervisor node in DT. So check if it needs to enable ACPI. >>> > > >>> > > Signed-off-by: Shannon Zhao >>> > > --- >>> > > arch/arm64/kernel/acpi.c | 12 ++++++++---- >>> > > 1 file changed, 8 insertions(+), 4 deletions(-) >>> > > >>> > > diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c >>> > > index d1ce8e2..4e92be0 100644 >>> > > --- a/arch/arm64/kernel/acpi.c >>> > > +++ b/arch/arm64/kernel/acpi.c >>> > > @@ -67,10 +67,13 @@ static int __init dt_scan_depth1_nodes(unsigned long node, >>> > > { >>> > > /* >>> > > * Return 1 as soon as we encounter a node at depth 1 that is >>> > > - * not the /chosen node. >>> > > + * not the /chosen node, or /hypervisor node when running on Xen. >>> > > */ >>> > > - if (depth == 1 && (strcmp(uname, "chosen") != 0)) >>> > > - return 1; >>> > > + if (depth == 1 && (strcmp(uname, "chosen") != 0)) { >>> > > + if (!xen_initial_domain() || (strcmp(uname, "hypervisor") != 0)) >>> > > + return 1; >>> > > + } >>> > > + >>> > > return 0; >>> > > } >> > >> > As this is changing the semantic of an "empty" DT, we should consider >> > now if there's anything else that might also need to exist in an "empty" >> > DT. We don't want to change this again in future if we don't have to, >> > given the compatiblity nightmare that's sure to result. >> > >> > We should also consider if the "hypervisor" node name is sufficient (I >> > think it is, but let's not assume anything). >>>From Xen point of view I think it is enough: real hardware is described > in ACPI anyway and anything hypervisor related can be done via > hypercalls once Xen support is discovered, for which the hypervisor node > is sufficient. Yes, I think the hypervisor node is sufficient for current Xen ACPI support. -- Shannon