From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 0/3] RFC: provide synchronous registers in kvm_run Date: Thu, 22 Dec 2011 14:35:45 +0200 Message-ID: <4EF32421.8000303@redhat.com> References: <20111222115646.248800653@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Marcelo Tossati , Carsten Otte , Alexander Graf , Jens Freimann , Cornelia Huck , Heiko Carstens , Martin Schwidefsky , KVM To: Christian Borntraeger Return-path: Received: from mx1.redhat.com ([209.132.183.28]:42262 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751195Ab1LVMf5 (ORCPT ); Thu, 22 Dec 2011 07:35:57 -0500 In-Reply-To: <20111222115646.248800653@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/22/2011 01:56 PM, Christian Borntraeger wrote: > Avi, Marcelo, > > currently userspace can access guest registers via several ioctls. Some > of these registers might be useful very often. Here the system call overhead > for ioctl can make an exit more expensive than necessary. > In a discussion with Alex Graf we concluded that it might be beneficial to > have a subset of registers available in kvm_run. (The ioctls will also be > available). > > This series provides a prototype implementation together with two example > users for s390. > > Interesting. Other archs emulate everything to do with registers in the kernel, so this is not a fast path. What workload does this benefit? -- error compiling committee.c: too many arguments to function