From mboxrd@z Thu Jan  1 00:00:00 1970
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH 2/2] KVM: PPC: Book3S: Implement floating-point state
 get/set functions
Date: Wed, 19 Sep 2012 13:37:42 +1000
Message-ID: <1348025862.2386.63.camel@pasglop>
References: <20120912001719.GE32642@bloggs.ozlabs.ibm.com>
	 <20120912001922.GG32642@bloggs.ozlabs.ibm.com>
	 <716EE2F4-D016-4009-A11A-0866C1A75995@suse.de>
	 <20120913235816.GB14036@bloggs.ozlabs.ibm.com>
	 <9E858BF2-180D-48D3-AD0D-89ACB9436554@suse.de>
	 <20120914013636.GA31335@drongo>
	 <C760C94D-2B91-42CB-9451-027D49F19229@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Paul Mackerras <paulus@samba.org>, kvm-ppc@vger.kernel.org,
	kvm@vger.kernel.org
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-ppc-owner@vger.kernel.org>
In-Reply-To: <C760C94D-2B91-42CB-9451-027D49F19229@suse.de>
Sender: kvm-ppc-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On Fri, 2012-09-14 at 03:44 +0200, Alexander Graf wrote:
> 
> We're slowly moving towards ONE_REG. ARM is already going full steam
> ahead and I'd like to have every new register in PPC be modeled with
> it as well. The old interface broke on us one time too often now :).
> 
> As I said, if we run into performance problems, we will implement ways
> to improve performance. At the end of the day, x86 will be the odd one
> out.

This is totally insane. In most cases, we care about the whole set of 32
registers. Doing 32 ioctl's for that is just plain stupid.

There is nothing wrong in allowing the "one reg" interface as well, but
it's totally ridiculous to *require* it.

Ben.