public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@redhat.com>,
	Avi Kivity <avi@redhat.com>, Pavel Machek <pavel@ucw.cz>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: v3.4-rc1 s2ram regression
Date: Mon, 02 Apr 2012 12:27:44 +0400	[thread overview]
Message-ID: <4F796300.5040905@openvz.org> (raw)
In-Reply-To: <20120401165354.GA18526@amt.cnet>

Marcelo Tosatti wrote:
> On Sun, Apr 01, 2012 at 05:26:43PM +0400, Konstantin Khlebnikov wrote:
>> commit b74f05d61b73af584d0c39121980171389ecfaaa
>> ("x86: kvmclock: abstract save/restore sched_clock_state")
>> breaks s2ram for my notebook. It hangs (maybe panic) somewhere on resume stage
>> and blinks with all possible leds =) Screen is black, so I don't know what happened.
>>
>> reverting or following patch helps
>>
>> Bisected-by: Konstantin Khlebnikov<khlebnikov@openvz.org>
>> Cc: Thomas Gleixner<tglx@linutronix.de>
>> Cc: Marcelo Tosatti<mtosatti@redhat.com>
>> Cc: Avi Kivity<avi@redhat.com>
>> Cc: Igor Mammedov<imammedo@redhat.com>
>> ---
>>   arch/x86/power/cpu.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/x86/power/cpu.c b/arch/x86/power/cpu.c
>> index 4793683..2bc5a82 100644
>> --- a/arch/x86/power/cpu.c
>> +++ b/arch/x86/power/cpu.c
>> @@ -231,8 +231,8 @@ static void __restore_processor_state(struct saved_context *ctxt)
>>   /* Needed by apm.c */
>>   void restore_processor_state(void)
>>   {
>> -	x86_platform.restore_sched_clock_state();
>>   	__restore_processor_state(&saved_context);
>> +	x86_platform.restore_sched_clock_state();
>>   }
>>   #ifdef CONFIG_X86_32
>>   EXPORT_SYMBOL(restore_processor_state);
>
> The correct fix is in kvm.git (see below).

Thanks. Your patch works for me too.

>
> Ingo, can you please merge it through x86 tree while the
> kvm.git issues are resolved? It has been forward to you directly.
>
>      x86: call restore_sched_clock_state after %gs is initialized
>
>      restore_sched_clock_state methods use percpu data, therefore they
>      must run after %gs is initialized, but before mtrr_bp_restore (due to
>      lockstat using sched_clock).
>
>      Move it to the correct place.
>
>      Signed-off-by: Marcelo Tosatti<mtosatti@redhat.com>
>      Signed-off-by: Avi Kivity<avi@redhat.com>
>
>


      parent reply	other threads:[~2012-04-02  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-01 13:26 [PATCH] x86: v3.4-rc1 s2ram regression Konstantin Khlebnikov
2012-04-01 16:53 ` Marcelo Tosatti
2012-04-02  7:27   ` Ingo Molnar
2012-04-02  8:27   ` Konstantin Khlebnikov [this message]

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=4F796300.5040905@openvz.org \
    --to=khlebnikov@openvz.org \
    --cc=avi@redhat.com \
    --cc=hpa@zytor.com \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --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