From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Lv Zheng <lv.zheng@intel.com>
Cc: Len Brown <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] ACPI: Default disable auto-serialization.
Date: Mon, 17 Mar 2014 13:09:12 +0100 [thread overview]
Message-ID: <5326E5E8.4070804@intel.com> (raw)
In-Reply-To: <fdc47fb7d89d984a164531b316e8b56f73ed05c9.1395028738.git.lv.zheng@intel.com>
On 3/17/2014 5:14 AM, Lv Zheng wrote:
> This feature enabled by the following commit is still under development.
>
> Commit: cd52379678785b02d7a357988cfba214fdaf92f4
> Subject: ACPICA: Add global option to disable method auto-serialization.
> This change adds an option to disable the auto-serialization of
> methods that create named objects.
>
> This patch disables it by default temporarily according to the bug reports.
Well, it doesn't restore the 3.14 behavior of acpi_auto_serialize, as
far as I can say, so we can't apply it.
I still can drop the commits related to auto-serialization from my
acpica branch. Which commits are they?
> References: http://www.spinics.net/lists/linux-acpi/msg49496.html
> Reported-by: Valdis Kletnieks <validis.kletnieks@vt.edu>
> Reported-by: Sabrina Dubroka <sd@queasysnail.net>
> Signed-off-by: Lv Zheng <lv.zheng@intel.com>
> ---
> Documentation/kernel-parameters.txt | 8 ++++----
> drivers/acpi/acpica/acglobal.h | 2 +-
> drivers/acpi/osl.c | 12 ++++++------
> 3 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 91f0be8..a159537 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -229,13 +229,13 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> use by PCI
> Format: <irq>,<irq>...
>
> - acpi_no_auto_serialize [HW,ACPI]
> - Disable auto-serialization of AML methods
> + acpi_auto_serialize [HW,ACPI]
> + Enable auto-serialization of AML methods
> AML control methods that contain the opcodes to create
> named objects will be marked as "Serialized" by the
> auto-serialization feature.
> - This feature is enabled by default.
> - This option allows to turn off the feature.
> + This feature is disabled by default.
> + This option allows to turn on the feature.
>
> acpi_no_auto_ssdt [HW,ACPI] Disable automatic loading of SSDT
>
> diff --git a/drivers/acpi/acpica/acglobal.h b/drivers/acpi/acpica/acglobal.h
> index 49bbc71..ea0f838 100644
> --- a/drivers/acpi/acpica/acglobal.h
> +++ b/drivers/acpi/acpica/acglobal.h
> @@ -99,7 +99,7 @@ ACPI_INIT_GLOBAL(u8, acpi_gbl_enable_interpreter_slack, FALSE);
> * that create named objects are marked Serialized in order to prevent
> * possible run-time problems if they are entered by more than one thread.
> */
> -ACPI_INIT_GLOBAL(u8, acpi_gbl_auto_serialize_methods, TRUE);
> +ACPI_INIT_GLOBAL(u8, acpi_gbl_auto_serialize_methods, FALSE);
>
> /*
> * Create the predefined _OSI method in the namespace? Default is TRUE
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index d40d6dc..928f0c2 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -1538,20 +1538,20 @@ static int __init osi_setup(char *str)
> __setup("acpi_osi=", osi_setup);
>
> /*
> - * Disable the auto-serialization of named objects creation methods.
> + * Enable the auto-serialization of named objects creation methods.
> *
> - * This feature is enabled by default. It marks the AML control methods
> + * This feature is disabled by default. It marks the AML control methods
> * that contain the opcodes to create named objects as "Serialized".
> */
> -static int __init acpi_no_auto_serialize_setup(char *str)
> +static int __init acpi_auto_serialize_setup(char *str)
> {
> - acpi_gbl_auto_serialize_methods = FALSE;
> - pr_info("ACPI: auto-serialization disabled\n");
> + acpi_gbl_auto_serialize_methods = TRUE;
> + pr_info("ACPI: auto-serialization enabled\n");
>
> return 1;
> }
>
> -__setup("acpi_no_auto_serialize", acpi_no_auto_serialize_setup);
> +__setup("acpi_auto_serialize", acpi_auto_serialize_setup);
>
> /* Check of resource interference between native drivers and ACPI
> * OperationRegions (SystemIO and System Memory only).
next prev parent reply other threads:[~2014-03-17 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 16:05 ACPICA 20140214 auto-serialize weirds my machine Valdis Kletnieks
2014-03-14 16:10 ` Rafael J. Wysocki
2014-03-14 17:24 ` Valdis.Kletnieks
2014-03-14 17:38 ` Sabrina Dubroca
2014-03-14 18:08 ` Sabrina Dubroca
2014-03-14 19:36 ` Moore, Robert
2014-03-14 20:04 ` Valdis.Kletnieks
2014-03-14 20:14 ` Moore, Robert
2014-03-14 21:02 ` Moore, Robert
2014-03-14 21:29 ` Moore, Robert
2014-03-17 1:18 ` Zheng, Lv
2014-03-17 4:13 ` [RFC PATCH 0/2] ACPICA: Updates for auto-serialization mechanism Lv Zheng
2014-03-17 4:14 ` [RFC PATCH 1/2] ACPICA: Dispatcher: Ignore SyncLevel " Lv Zheng
2014-03-18 0:50 ` Zheng, Lv
2014-03-18 22:58 ` Sabrina Dubroca
2014-03-17 4:14 ` [RFC PATCH 2/2] ACPI: Default disable auto-serialization Lv Zheng
2014-03-17 12:09 ` Rafael J. Wysocki [this message]
2014-03-18 0:31 ` Zheng, Lv
2014-03-18 1:13 ` Rafael J. Wysocki
2014-03-18 1:29 ` Zheng, Lv
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=5326E5E8.4070804@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=zetalog@gmail.com \
/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