public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lv Zheng <lv.zheng@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Len Brown <len.brown@intel.com>
Cc: Lv Zheng <lv.zheng@intel.com>, Lv Zheng <zetalog@gmail.com>,
	linux-acpi@vger.kernel.org
Subject: [PATCH 0/5] ACPICA: Merge auto-serialization support to reduce source code differences between Linux and ACPICA upstream.
Date: Mon, 24 Mar 2014 14:48:26 +0800	[thread overview]
Message-ID: <cover.1395638745.git.lv.zheng@intel.com> (raw)

The auto-serialization feature is introduced in ACPICA 20140214 release, it
is reverted due to the new bug reports.
The feature fixes a compliance issue between the ACPICA interpreter and the
de-facto implementation.  Users are encouraged to use this feature to
provide the feedbacks.

This series re-orders the patches to implement the feature so that it can
be marked out by reverting the last patch in this series when new problems
are detected.
This series can also reduce the source code differences between Linux and
ACPICA upstream.

Bob Moore (2):
  ACPICA: Add auto-serialization support for ill-behaved control
    methods.
  ACPICA: Ignore sync_level for methods that have been auto-serialized.

Lv Zheng (3):
  ACPICA: Remove global option to serialize all control methods.
  ACPICA: Add additional named objects for the auto-serialize method
    scan.
  ACPICA: Enable auto-serialization as a default kernel behavior.

 Documentation/kernel-parameters.txt |   10 ++-
 drivers/acpi/acpica/acdispat.h      |   13 +--
 drivers/acpi/acpica/acglobal.h      |   11 +--
 drivers/acpi/acpica/acinterp.h      |    4 -
 drivers/acpi/acpica/acobject.h      |    3 +-
 drivers/acpi/acpica/acstruct.h      |    3 +
 drivers/acpi/acpica/dsinit.c        |   59 ++++++++++---
 drivers/acpi/acpica/dsmethod.c      |  156 +++++++++++++++++++++++++++++++++--
 drivers/acpi/acpica/dswload.c       |   16 ++++
 drivers/acpi/acpica/exsystem.c      |   12 +--
 drivers/acpi/acpica/exutils.c       |   80 +++---------------
 drivers/acpi/acpica/nsinit.c        |    5 +-
 drivers/acpi/acpica/nsload.c        |    4 +-
 drivers/acpi/acpica/psloop.c        |    4 +
 drivers/acpi/acpica/psobject.c      |    7 +-
 drivers/acpi/osl.c                  |   16 ++--
 include/acpi/acpixf.h               |    2 +-
 17 files changed, 281 insertions(+), 124 deletions(-)

-- 
1.7.10


             reply	other threads:[~2014-03-24  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:48 Lv Zheng [this message]
2014-03-24  6:48 ` [PATCH 1/5] ACPICA: Remove global option to serialize all control methods Lv Zheng
2014-03-24  6:49 ` [PATCH 2/5] ACPICA: Add auto-serialization support for ill-behaved " Lv Zheng
2014-03-24  6:49 ` [PATCH 3/5] ACPICA: Add additional named objects for the auto-serialize method scan Lv Zheng
2014-03-24  6:49 ` [PATCH 4/5] ACPICA: Ignore sync_level for methods that have been auto-serialized Lv Zheng
2014-03-24  6:49 ` [PATCH 5/5] ACPICA: Enable auto-serialization as a default kernel behavior Lv Zheng

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.1395638745.git.lv.zheng@intel.com \
    --to=lv.zheng@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael.j.wysocki@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