From: Paolo Bonzini <pbonzini@redhat.com>
To: James Hogan <james.hogan@imgtec.com>, Ralf Baechle <ralf@linux-mips.org>
Cc: Sanjay Lal <sanjayl@kymasys.com>, Gleb Natapov <gleb@kernel.org>,
kvm@vger.kernel.org, linux-mips@linux-mips.org,
stable@vger.kernel.org
Subject: Re: [PATCH] KVM: MIPS: Don't leak FPU/DSP to guest
Date: Tue, 10 Feb 2015 09:01:07 +0100 [thread overview]
Message-ID: <54D9BAC3.9080300@redhat.com> (raw)
In-Reply-To: <20150209225816.GH30459@jhogan-linux.le.imgtec.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/02/2015 23:58, James Hogan wrote:
>> First lets save and disable the FPU (and MSA) state with
>> lose_fpu(1)
>
> Please don't apply this patch yet. lose_fpu() uses function
> symbols which aren't exported for modules to use yet, so that'll
> need fixing first or KVM won't build as a module.
Well, too late. :)
James/Ralf, should I revert, or can that be fixed during the RC period?
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJU2brAAAoJEL/70l94x66DdXIIAImur1pdSKYWw1+FzZH+H8Xo
86j9EfptORk554o0a62LG9dOTY+5sJfAV9CoB7Q+8IfdLDKxpk1sLjMkiS0E0EWU
2ilQfjYEXLTgCW38p03ype4m6g4uSfT16dnizrwnUviFk/EvVgCWHy88tA3+Vfn/
WgoxcXkd+hguyNaLR2oAVqyNhAETLTo4kQQqKwGbXFXf0GLno44pj7bJprCR/jlO
4+sUzuV5dno/GI6z8dyMmASo0QEy+IoXJ+aSw+IoRED9nlBMAS4+7uD4XfocGpca
En5KmXVnyJoazgV3Y6w2ymS606S0JNGRcOzqr8ZbOHtjJmAsZxjuVxP6PVzZqQg=
=ozzu
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-02-10 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:06 [PATCH] KVM: MIPS: Don't leak FPU/DSP to guest James Hogan
2015-02-04 17:06 ` James Hogan
2015-02-09 22:58 ` James Hogan
2015-02-09 22:58 ` James Hogan
2015-02-10 8:01 ` Paolo Bonzini [this message]
2015-02-10 8:17 ` James Hogan
2015-02-10 8:17 ` James Hogan
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=54D9BAC3.9080300@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sanjayl@kymasys.com \
--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 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.