From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: nd@arm.com, shankerd@codeaurora.org, xen-devel@lists.xen.org
Subject: Re: [PATCH 3/8] xen/arm: acpi: Don't fallback on DT when user request ACPI
Date: Mon, 20 Feb 2017 08:47:30 +0000 [thread overview]
Message-ID: <bf9fccdb-43ef-8130-68b4-a5545833ac02@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1702151739520.9566@sstabellini-ThinkPad-X260>
Hi Stefano,
On 02/16/2017 01:41 AM, Stefano Stabellini wrote:
> On Fri, 3 Feb 2017, Julien Grall wrote:
>> On ARM, when the user put 'acpi=force' Xen will use ACPI over DT.
>> Currently, if Xen fails to initialize ACPI it will fallback on DT.
>>
>> This behavior makes difficult for a user to notice Xen didn't used ACPI
>> has requested on platform where the firmware is providing both ACPI and DT.
>>
>> Rather than fallback on DT during a failure, panic when 'acpi=force'.
>>
>> Signed-off-by: Julien Grall <julien.grall@arm.com>
>>
>> ---
>> I am wondering if we should do the same with acpi=on. So a user
>> would notice directly if something went wrong with ACPI.
>> Otherwise you would boot up to the prompt and barely notice that DT
>> was used.
>
> I would keep the current behavior as is and add new parameter that means
> "acpi and only acpi". Today acpi=force means "acpi is preferred to
> device tree". It doesn't mean that if acpi fail, Xen should panic.
>
> Maybe acpi=strict or acpi=mandatory?
We have a bunch of option that makes little sense today:
- off: Turned off ACPI
- on: Turned on ACPI only if DT is empty
- force: Turned on ACPI
If ACPI fails you fallback on DT. This is a pain to detect whether DT or
ACPI is been used. So I think adding another option will only confuse
the user.
Looking at Linux the option are:
- off: Turned off ACPI
- on: Prefer ACPI over DT. Fallback on DT is failed
- force: Use ACPI and panic if not available
I would much prefer to use the behavior of the acpi param on Linux
because it will avoid the user to be confused on the usage.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-20 8:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 19:18 [PATCH 0/8] xen/arm: Fix and clean-up for ACPI and EFI Julien Grall
2017-02-03 19:18 ` [PATCH 1/8] xen/arm: acpi: Handle correctly detection of GICv2 on GICv3 Julien Grall
2017-02-16 1:36 ` Stefano Stabellini
2017-02-03 19:18 ` [PATCH 1/7] xen/arm: acpi: Rework acpi_boot_table_init error paths Julien Grall
2017-02-03 22:09 ` Wei Liu
2017-02-03 19:18 ` [PATCH 2/7] xen/arm: acpi: Don't fallback on DT when user request ACPI Julien Grall
2017-02-03 19:18 ` [PATCH 2/8] xen/arm: acpi: Rework acpi_boot_table_init error paths Julien Grall
2017-02-03 20:44 ` Andrew Cooper
2017-02-08 18:25 ` Julien Grall
2017-02-16 1:39 ` Stefano Stabellini
2017-02-03 19:18 ` [PATCH 3/8] xen/arm: acpi: Don't fallback on DT when user request ACPI Julien Grall
2017-02-16 1:41 ` Stefano Stabellini
2017-02-20 8:47 ` Julien Grall [this message]
2017-02-20 18:12 ` Stefano Stabellini
2017-02-20 18:13 ` Julien Grall
2017-03-03 18:35 ` Julien Grall
2017-02-03 19:18 ` [PATCH 3/7] xen/arm: Print whether Xen is booting using ACPI or DT Julien Grall
2017-02-03 19:18 ` [PATCH 4/7] xen/arm: efi: Avoid duplicating the addition of a new bank Julien Grall
2017-02-03 19:18 ` [PATCH 4/8] xen/arm: Print whether Xen is booting using ACPI or DT Julien Grall
2017-02-16 1:42 ` Stefano Stabellini
2017-02-03 19:18 ` [PATCH 5/8] xen/arm: efi: Avoid duplicating the addition of a new bank Julien Grall
2017-02-16 1:47 ` Stefano Stabellini
2017-02-16 1:49 ` Stefano Stabellini
2017-03-03 18:31 ` Julien Grall
2017-02-03 19:18 ` [PATCH 6/8] xen/arm: efi: Avoid duplicating the addition of a new efi memory descriptor Julien Grall
2017-02-16 1:52 ` Stefano Stabellini
2017-02-03 19:18 ` [PATCH 6/7] xen/arm: efi: Rework acpi_create_efi_mmap_table to avoid memory_map[offset] Julien Grall
2017-02-03 19:18 ` [PATCH 7/7] xen/arm: acpi: Move the ACPI banks in bootinfo Julien Grall
2017-02-03 19:18 ` [PATCH 7/8] xen/arm: efi: Rework acpi_create_efi_mmap_table to avoid memory_map[offset] Julien Grall
2017-02-16 1:57 ` Stefano Stabellini
2017-02-03 19:18 ` [PATCH 8/8] xen/arm: acpi: Move the ACPI banks in bootinfo Julien Grall
2017-02-16 2:00 ` Stefano Stabellini
2017-02-16 1:58 ` [PATCH 0/8] xen/arm: Fix and clean-up for ACPI and EFI Stefano Stabellini
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=bf9fccdb-43ef-8130-68b4-a5545833ac02@arm.com \
--to=julien.grall@arm.com \
--cc=nd@arm.com \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).