From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S936032AbdKPWNb (ORCPT <rfc822;w@1wt.eu>);
        Thu, 16 Nov 2017 17:13:31 -0500
Received: from mail-pg0-f66.google.com ([74.125.83.66]:39731 "EHLO
        mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S933850AbdKPWNX (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 16 Nov 2017 17:13:23 -0500
X-Google-Smtp-Source: AGs4zMZi5uIdCKgJ9odULNqrJy/GfakbzFOmAWBEMUhgbKcamkToBOaDRoH54jflgcoXY+pQ+rUhmQ==
Date: Thu, 16 Nov 2017 14:13:20 -0800
From: Guenter Roeck <linux@roeck-us.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andi Kleen <ak@linux.intel.com>, x86@kernel.org, hpa@zytor.com,
        linux-kernel@vger.kernel.org
Subject: Re: [v8, 4/5] x86/xsave: Make XSAVE check the base CPUID features
 before enabling
Message-ID: <20171116221320.GA20005@roeck-us.net>
References: <20171005215256.25659-5-andi@firstfloor.org>
 <20171111231521.GA31139@roeck-us.net>
 <20171112064148.GL8522@tassilo.jf.intel.com>
 <20171114012805.GD2482@two.firstfloor.org>
 <20171114014915.GA23102@roeck-us.net>
 <20171116190347.GF2482@two.firstfloor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171116190347.GF2482@two.firstfloor.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Nov 16, 2017 at 11:03:47AM -0800, Andi Kleen wrote:
> > It is what I use at kerneltests.org.
> > See https://github.com/groeck/linux-build-test/tree/master/rootfs/x86_64
> > for configuration and script.
> > 
> > > I can't reproduce it here with different qemu settings.
> > > 
> > Interesting. What version of qemu are you using ?
> 
> I tested with your config: -no-kvm -cpu Broadwell-noTSX -M q35 and still
> don't see any boot warnings. This is 
> 
> QEMU emulator version 2.9.1(qemu-2.9.1-2.fc26)
> 
> If you're on an older version it may be already fixed in qemu then.
> 

I see the problem with both qemu 2.9.1 and 2.10.1. Interestingly, I don't
see it with an official Debian 2.5.0 build. Maybe it is the result of some
configuration option in my build.

Let's just ignore it for now.

Guenter