qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] CVE-2017-5715: relevant qemu patches
Date: Thu, 4 Jan 2018 13:53:44 +0100	[thread overview]
Message-ID: <4baad7ed-8f1f-3f7a-c051-a12dd9a030ac@profihost.ag> (raw)
In-Reply-To: <6d95cc4b-155c-44cb-1fc0-18ba848741ac@profihost.ag>

Nobody? Is this something they did on their own?

Stefan

Am 04.01.2018 um 07:27 schrieb Stefan Priebe - Profihost AG:
> Hello,
> 
> i've seen some vendors have updated qemu regarding meltdown / spectre.
> 
> f.e.:
> 
>  CVE-2017-5715: QEMU was updated to allow passing through new MSR and
>      CPUID flags from the host VM to the CPU, to allow enabling/disabling
>      branch prediction features in the Intel CPU. (bsc#1068032)
> 
> Can anybody point me to the relevant qemu patches?
> 
> Thanks!
> 
> Greets,
> Stefan
> 

      parent reply	other threads:[~2018-01-04 12:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  6:27 [Qemu-devel] CVE-2017-5715: relevant qemu patches Stefan Priebe - Profihost AG
2018-01-04  7:24 ` Alexandre DERUMIER
2018-01-04  7:27   ` Alexandre DERUMIER
2018-01-04  8:17     ` Stefan Priebe - Profihost AG
2018-01-04  8:35       ` Alexandre DERUMIER
2018-01-04  9:22         ` Stefan Priebe - Profihost AG
2018-01-04 15:53         ` Paolo Bonzini
2018-01-04 20:15           ` Stefan Priebe - Profihost AG
2018-01-05  8:33             ` Paolo Bonzini
2018-01-05 10:40               ` Stefan Priebe - Profihost AG
2018-01-05 10:57                 ` Paolo Bonzini
2018-01-04 12:53 ` Stefan Priebe - Profihost AG [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=4baad7ed-8f1f-3f7a-c051-a12dd9a030ac@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=qemu-devel@nongnu.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).