linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, hpa@zytor.com
Cc: ming.m.lin@intel.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, lenb@kernel.org,
	linux-acpi@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT PULL/PATCH] gts and bfs fixes (v5).
Date: Mon, 23 Apr 2012 13:34:51 +0200	[thread overview]
Message-ID: <201204231334.51376.rjw@sisk.pl> (raw)
In-Reply-To: <1335150198-21899-1-git-send-email-konrad.wilk@oracle.com>

On Monday, April 23, 2012, Konrad Rzeszutek Wilk wrote:
> Please git pull (or use the patches that follow this email) the following branch:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-x86-for-3.4
> 
> Changes since v4 [https://lkml.org/lkml/2012/4/18/396]
>  - Added Acked and Reviewed-by
> v2 [https://lkml.org/lkml/2012/4/9/474]
>  - ditched the assembler version and used a C wrapper
> 
> With git commit a2ef5c4fd44ce3922435139393b89f2cce47f576
> "ACPI: Move module parameter gts and bfs to sleep.c" the
> sampling of gts/bfs module parameters flag by acpi_enter_sleep_state
> has been moved. It has been moved out of the inner ACPI code and
> out in the more x86 specific. This means that any caller of
> the exported acpi_enter_sleep_state function needs to provide
> two parameters now: sleep state and the bit flag whether to us _GTS|_BFS.
> 
> All of the callers of acpi_enter_sleep_state did that, with
> the exception of the assembler version and as well any
> third-party callers of acpi_enter_sleep_state.
> 
> These two patches expose 'wake_sleep_flags' as the product
> of the gts/bfs module parameter invocation. And also use said
> flag in the assembler 'do_suspend_lowlevel()' function.
> 
> Konrad Rzeszutek Wilk (2):
>       ACPI: Convert wake_sleep_flags to a value instead of function (v5)
>       x86/acpi: Call acpi_enter_sleep_state via an asmlinkage C function from assembler (v2).
> 
>  arch/x86/kernel/acpi/sleep.c     |    4 +++
>  arch/x86/kernel/acpi/sleep.h     |    4 +++
>  arch/x86/kernel/acpi/wakeup_32.S |    4 +--
>  arch/x86/kernel/acpi/wakeup_64.S |    4 +--
>  drivers/acpi/sleep.c             |   52 ++++++++++++++++++++-----------------
>  5 files changed, 38 insertions(+), 30 deletions(-)

Peter, are you going to take this?

Rafael

  parent reply	other threads:[~2012-04-23 11:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23  3:03 [GIT PULL/PATCH] gts and bfs fixes (v5) Konrad Rzeszutek Wilk
2012-04-23  3:03 ` [PATCH 1/2] ACPI: Convert wake_sleep_flags to a value instead of function (v5) Konrad Rzeszutek Wilk
2012-04-23  3:03 ` [PATCH 2/2] x86/acpi: Call acpi_enter_sleep_state via an asmlinkage C function from assembler (v2) Konrad Rzeszutek Wilk
2012-04-23 11:34 ` Rafael J. Wysocki [this message]
2012-04-23 17:34   ` [GIT PULL/PATCH] gts and bfs fixes (v5) H. Peter Anvin
2012-04-23 17:39     ` Konrad Rzeszutek Wilk
2012-04-23 18:00       ` H. Peter Anvin

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=201204231334.51376.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=x86@kernel.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).