From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/9] x86: export get_xsave_addr
Date: Thu, 04 Dec 2014 18:29:03 +0100
Message-ID: <548099DF.4080202@redhat.com>
References: <1417708634-24333-1-git-send-email-pbonzini@redhat.com> <1417708634-24333-2-git-send-email-pbonzini@redhat.com> <20141204163443.GA1477@kroah.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	rkrcmar@redhat.com, Wanpeng Li <wanpeng.li@linux.intel.com>,
	stable@vger.kernel.org, x86@kernel.org,
	"H. Peter Anvin" <hpa@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Return-path: <stable-owner@vger.kernel.org>
In-Reply-To: <20141204163443.GA1477@kroah.com>
Sender: stable-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org



On 04/12/2014 17:34, Greg KH wrote:
> On Thu, Dec 04, 2014 at 04:57:06PM +0100, Paolo Bonzini wrote:
>> > get_xsave_addr is the API to access XSAVE states, and KVM would
>> > like to use it.  Export it.
> Use it in what way?

As in patch 2/9, to avoid that upgrading to a newer processor breaks
userspace ABI.

>> > Cc: stable@vger.kernel.org
> Why is this a stable patch?

Because as of now, Skylake processors have a different userspace ABI
than previous generations.

Paolo