From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63A16C432C2 for ; Wed, 25 Sep 2019 21:37:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4134921D80 for ; Wed, 25 Sep 2019 21:37:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728142AbfIYVhe convert rfc822-to-8bit (ORCPT ); Wed, 25 Sep 2019 17:37:34 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:38547 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728016AbfIYVhe (ORCPT ); Wed, 25 Sep 2019 17:37:34 -0400 Received: from localhost ([127.0.0.1] helo=flow.W.breakpoint.cc) by Galois.linutronix.de with esmtp (Exim 4.80) (envelope-from ) id 1iDEyW-0002Dx-Np; Wed, 25 Sep 2019 23:37:28 +0200 From: Sebastian Andrzej Siewior To: kvm@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Paolo Bonzini , =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?= , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org Subject: KVM: x86: Pass additional FPU bits to the guest Date: Wed, 25 Sep 2019 23:37:19 +0200 Message-Id: <20190925213721.21245-1-bigeasy@linutronix.de> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While testing my FPU patches on AMD's ZEN platform I noticed that the XSAVES feature flag was never used in the guest while it was present in the host. Patch #1 seemed to work but I holded on to it because I could explain why the guest did report ´fxsave_leak' while the host did not. It turns out that I need #2 _and_ tell qemu not to mask this information away. Sebastian