From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: (partial) Spectre v2 mitigation without on Skylake IBRS
Date: Mon, 26 Feb 2018 14:53:45 +0100 [thread overview]
Message-ID: <12c4444e-4fce-5657-277f-f9b5abfd6304@suse.com> (raw)
In-Reply-To: <5A94159A02000078001ABCCD@suse.com>
On 26/02/18 14:11, Jan Beulich wrote:
>>>> On 26.02.18 at 13:36, <jgross@suse.com> wrote:
>> On 26/02/18 11:49, Jan Beulich wrote:
>>>>>> On 26.02.18 at 11:18, <jgross@suse.com> wrote:
>>>> If this is the case I believe the easiest solution would be to let the
>>>> kernel set the MSR again after leaving suspended state. suspend/resume
>>>> require hooks in pv kernels after all.
>>>
>>> Hmm, this could be leveraged irrespective of what I've written
>>> above - the kernel could then also clear the MSR during suspend,
>>> thus allowing the check in libxc to pass.
>>
>> Something like the attached patch?
>
> With proper checking added of whether the MSR actually exists,
> yes, I think so. Will need to see how this can be converted to
> something that works on the old XenoLinux trees.
Okay, will post the (modified) patch to lkml.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-02-26 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 9:44 (partial) Spectre v2 mitigation without on Skylake IBRS Jan Beulich
2018-02-26 10:18 ` Juergen Gross
2018-02-26 10:49 ` Jan Beulich
[not found] ` <5A93F44E02000078001ABA67@suse.com>
2018-02-26 12:36 ` Juergen Gross
2018-02-26 13:11 ` Jan Beulich
[not found] ` <5A94159A02000078001ABCCD@suse.com>
2018-02-26 13:53 ` Juergen Gross [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=12c4444e-4fce-5657-277f-f9b5abfd6304@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).