Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755039Ab0KPRH5 (ORCPT ); Tue, 16 Nov 2010 12:07:57 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60079 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754627Ab0KPRHz (ORCPT ); Tue, 16 Nov 2010 12:07:55 -0500 Message-ID: <4CE2BA2F.6010306@redhat.com> Date: Tue, 16 Nov 2010 19:06:55 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101103 Fedora/1.0-0.33.b2pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.6 MIME-Version: 1.0 To: Peter Zijlstra CC: Martin Schwidefsky , Michael Holzheu , Shailabh Nagar , Andrew Morton , Venkatesh Pallipadi , Suresh Siddha , Ingo Molnar , Oleg Nesterov , John stultz , Thomas Gleixner , Balbir Singh , Heiko Carstens , Roland McGrath , linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, "jeremy.fitzhardinge" Subject: Re: [RFC][PATCH v2 4/7] taskstats: Add per task steal time accounting References: <20101111170352.732381138@linux.vnet.ibm.com> <20101111170815.024542355@linux.vnet.ibm.com> <1289677083.2109.167.camel@laptop> <20101115155057.15f3be35@mschwide.boeblingen.de.ibm.com> <1289833883.2109.494.camel@laptop> <20101115184206.4463fd05@mschwide.boeblingen.de.ibm.com> <1289843441.2109.520.camel@laptop> <20101115185923.1c353d07@mschwide.boeblingen.de.ibm.com> <1289844524.2109.524.camel@laptop> <20101116095101.5d86d1e5@mschwide.boeblingen.de.ibm.com> <1289909768.2109.592.camel@laptop> <20101116163325.755a709f@mschwide.boeblingen.de.ibm.com> <1289922329.2109.627.camel@laptop> <4CE2B37F.8050808@redhat.com> <1289925806.2109.628.camel@laptop> <4CE2B7CC.9010708@redhat.com> In-Reply-To: <4CE2B7CC.9010708@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 983 Lines: 24 On 11/16/2010 06:56 PM, Avi Kivity wrote: > On 11/16/2010 06:43 PM, Peter Zijlstra wrote: >> >>> No. Hypercalls are voluntary and known, but most exits are involuntary >>> and unknown to the guest. Any memory access can generate a page fault, >>> and any host interrupt will exit the guest. >> Right, but we could not make the guest jump to a special stub on vcpu >> enter? I guess we could simply because we have the hypervisor under >> control. > > No, some entries inject an interrupt or exception, so the next rip > value is unknown (without doing a lot of extra slow calculations). Also, consider an exit within the stub (if the stub is paged out, for example). -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/