All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lv Zheng <zetalog@gmail.com>
To: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Lv Zheng <lv.zheng@intel.com>
Subject: [PATCH v2 0/3] ACPICA: Interpreter: Fix regressions in lock order improvement
Date: Wed, 26 Oct 2016 15:39:55 +0800	[thread overview]
Message-ID: <cover.1477465173.git.lv.zheng@intel.com> (raw)
In-Reply-To: <cover.1477372449.git.lv.zheng@intel.com>

This patchset fixes regressions in ACPICA intepreter lock order
improvement.

Patches tested with customized ACPI table where _PS0/_PS3 methods are
customized to invoke a serialized control method which creates named
objects. When pm_async=yes, AE_ALREADY_EXISTS can be seen in suspend/resume
process. This is an existing issue, triggered in 4.9-rc1 by ACPICA
interpreter lock order fixes, and can be fixed by [PATCH 1] in this series.

v2:
1. Remove non-regression-fixes.
2. Add "Fixes" tags.

Lv Zheng (3):
  ACPICA: Dispatcher: Fix order issue of method termination
  ACPICA: Dispatcher: Fix an unbalanced lock exit path in
    acpi_ds_auto_serialize_method()
  ACPICA: Dispatcher: Tune interpreter lock around
    acpi_ev_initialize_region()

 drivers/acpi/acpica/dsinit.c   | 11 +++-------
 drivers/acpi/acpica/dsmethod.c | 50 +++++++++++++++++++-----------------------
 drivers/acpi/acpica/dswload2.c |  2 --
 drivers/acpi/acpica/evrgnini.c |  3 +++
 drivers/acpi/acpica/nsload.c   |  2 ++
 5 files changed, 30 insertions(+), 38 deletions(-)

-- 
2.7.4


  parent reply	other threads:[~2016-10-26  7:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25  5:20 [PATCH 0/6] ACPICA: Interpreter: Improve lock order fixes Lv Zheng
2016-10-25  5:21 ` [PATCH 1/6] ACPICA: Dispatcher: Fix order issue of method termination Lv Zheng
2016-10-25  5:21 ` [PATCH 2/6] ACPICA: Dispatcher: Fix an unbalanced lock exit path in acpi_ds_auto_serialize_method() Lv Zheng
2016-10-25  5:21 ` [PATCH 3/6] ACPICA: Dispatcher: Tune interpreter lock around acpi_ev_initialize_region() Lv Zheng
2016-10-25  5:21 ` [PATCH 4/6] ACPICA: Events: Cleanup acpi_ev_initialize_region() Lv Zheng
2016-10-25  5:21 ` [PATCH 5/6] ACPICA: Tables: Cleanup acpi_tb_install_and_load_table() Lv Zheng
2016-10-25  5:21 ` [PATCH 6/6] ACPICA: Tables: Add acpi_tb_unload_table() Lv Zheng
2016-10-26  0:51 ` [PATCH 0/6] ACPICA: Interpreter: Improve lock order fixes Rafael J. Wysocki
2016-10-26  6:17   ` Zheng, Lv
2016-10-26  7:05     ` Zheng, Lv
2016-10-26  7:39 ` Lv Zheng [this message]
2016-10-26  7:40   ` [PATCH v2 1/3] ACPICA: Dispatcher: Fix order issue of method termination Lv Zheng
2016-10-26  7:40   ` [PATCH v2 2/3] ACPICA: Dispatcher: Fix an unbalanced lock exit path in acpi_ds_auto_serialize_method() Lv Zheng
2016-10-26  7:42   ` [PATCH v2 3/3] ACPICA: Dispatcher: Tune interpreter lock around acpi_ev_initialize_region() Lv Zheng
2016-10-27 10:22   ` [PATCH v2 0/3] ACPICA: Interpreter: Fix regressions in lock order improvement Rafael J. Wysocki

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=cover.1477465173.git.lv.zheng@intel.com \
    --to=zetalog@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.