From: Ingo Molnar <mingo@kernel.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: x86@kernel.org, tglx@linutronix.de,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
mingo@redhat.com, Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
hpa@zytor.com
Subject: Re: [Xen-devel] [PATCH] x86/xen: zero MSR_IA32_SPEC_CTRL before suspend
Date: Thu, 12 Apr 2018 09:32:19 +0200 [thread overview]
Message-ID: <20180412073219.2h5fqc7megvepoa6@gmail.com> (raw)
In-Reply-To: <5ACE149E02000078001BA424@prv1-mh.provo.novell.com>
* Jan Beulich <JBeulich@suse.com> wrote:
> >>> On 11.04.18 at 13:53, <mingo@kernel.org> wrote:
> > * Jan Beulich <JBeulich@suse.com> wrote:
> >
> >> Additionally, x86 maintainers: is there a particular reason this (or
> >> any functionally equivalent patch) isn't upstream yet? As indicated
> >> before, I had not been able to find any discussion, and hence I
> >> see no reason why this is a patch we effectively carry privately in
> >> our distro branches (and likely other distros do so too).
> >
> > The patch was merged 6 weeks ago and is now upstream:
> >
> > 71c208dd54ab: x86/xen: Zero MSR_IA32_SPEC_CTRL before suspend
>
> I'm sorry, but no, this isn't the patch I was inquiring about.
> Instead I'm wondering of the disposition of the patch disabling
> IBRS around a CPU going idle.
Got any specific link or subject line for that submission?
Thanks,
Ingo
next prev parent reply other threads:[~2018-04-12 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 14:08 Juergen Gross
2018-02-26 16:17 ` Jan Beulich
2018-02-28 15:07 ` [tip:x86/pti] x86/xen: Zero " tip-bot for Juergen Gross
2018-03-14 8:48 ` [PATCH] x86/xen: zero " Jan Beulich
[not found] ` <5AA8F00302000078001B15EE@suse.com>
2018-04-11 7:08 ` Juergen Gross
2018-04-11 9:15 ` Jan Beulich
2018-04-11 11:53 ` [Xen-devel] " Ingo Molnar
2018-04-11 11:58 ` Jan Beulich
2018-04-12 7:32 ` Ingo Molnar [this message]
2018-04-12 7:53 ` Jan Beulich
2018-04-12 8:08 ` 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=20180412073219.2h5fqc7megvepoa6@gmail.com \
--to=mingo@kernel.org \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
Powered by JetHome