stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Matlack <dmatlack@google.com>
Cc: kvm list <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	stable@vger.kernel.org
Subject: Re: [PATCH] kvm: x86: do not leak guest xcr0 into host interrupt handlers
Date: Fri, 8 Apr 2016 18:50:17 +0200	[thread overview]
Message-ID: <5707E149.4020703@redhat.com> (raw)
In-Reply-To: <CALzav=fzqY62tMsD9H_7eiimvvy9JpuAPgZT-yQKb6zLaetCzQ@mail.gmail.com>



On 08/04/2016 18:25, David Matlack wrote:
> On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>
>>> Thank you :). Let me know how testing goes.
>>
>> It went well.
> 
> Great! How should we proceed?

It will appear very soon on kvm/next and Radim will send the pull
request to Linus next week (I'm having him practice before I go on
vacation ;)).

Paolo

  reply	other threads:[~2016-04-08 16:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 19:24 [PATCH] kvm: x86: do not leak guest xcr0 into host interrupt handlers David Matlack
2016-03-31  8:05 ` Paolo Bonzini
2016-04-05 11:28 ` Paolo Bonzini
2016-04-05 15:56   ` David Matlack
2016-04-05 16:07     ` Paolo Bonzini
2016-04-07  9:08     ` Paolo Bonzini
2016-04-07 18:18       ` David Matlack
2016-04-07 19:03         ` Paolo Bonzini
2016-04-08 16:25           ` David Matlack
2016-04-08 16:50             ` Paolo Bonzini [this message]
2016-04-08 16:54               ` David Matlack
2016-04-22  7:30 ` Wanpeng Li
2016-04-22 17:21   ` David Matlack
2016-04-23 22:37     ` Wanpeng Li
  -- strict thread matches above, loose matches on Subject: below --
2017-09-05  7:46 Lizhen You
2017-09-07 14:40 ` Greg KH
2017-09-08  1:28   ` You, Lizhen

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=5707E149.4020703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).