All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>, Borislav Petkov <bpetkov@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Zhang Rui <rui.zhang@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH urgent 0/3] __restore_processor_state() fixes
Date: Fri, 15 Dec 2017 11:18:28 +0200	[thread overview]
Message-ID: <001475f3-ad4c-4d89-dec2-362f7e28da33@linux.intel.com> (raw)
In-Reply-To: <2218120.DOUuxV87Xe@aspire.rjw.lan>

On 12/15/2017 03:28 AM, Rafael J. Wysocki wrote:
> On Thursday, December 14, 2017 10:19:04 PM CET Andy Lutomirski wrote:
>> __restore_processor_state() was spaghetti code, made no sense, and
>> had bugs.  And I broke resume on 32-bit systems.  This series cleans
>> it up and fixes it (hopefully!).
>>
>> Andy Lutomirski (3):
>>    x86/power/64: Use struct desc_ptr for the IDT in struct saved_context
>>    x86/power/32: Move SYSENTER MSR restoration to fix_processor_context()
>>    x86/power: Make restore_processor_context() sane
> 
> For all three:
> 
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
Works still after split up so my tested by remains. Please note Pavel 
gave his reported/tested-by in 3/3.

-- 
Jarkko

  parent reply	other threads:[~2017-12-15  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 21:19 [PATCH urgent 0/3] __restore_processor_state() fixes Andy Lutomirski
2017-12-14 21:19 ` [PATCH urgent 1/3] x86/power/64: Use struct desc_ptr for the IDT in struct saved_context Andy Lutomirski
2017-12-15 14:37   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-12-14 21:19 ` [PATCH urgent 2/3] x86/power/32: Move SYSENTER MSR restoration to fix_processor_context() Andy Lutomirski
2017-12-15 14:38   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-12-14 21:19 ` [PATCH urgent 3/3] x86/power: Make restore_processor_context() sane Andy Lutomirski
2017-12-14 22:32   ` Pavel Machek
2017-12-15 14:38   ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2017-12-15  1:28 ` [PATCH urgent 0/3] __restore_processor_state() fixes Rafael J. Wysocki
2017-12-15  1:35   ` Linus Torvalds
2017-12-15 11:21     ` Ingo Molnar
2017-12-15  9:18   ` Jarkko Nikula [this message]
2017-12-15 11:31     ` Ingo Molnar

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=001475f3-ad4c-4d89-dec2-362f7e28da33@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=bpetkov@suse.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=torvalds@linux-foundation.org \
    --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 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.