From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: Suggestions for testing VAPIC / TPR patching Date: Thu, 19 Jan 2012 11:02:19 +0200 Message-ID: <20120119090219.GG9571@redhat.com> References: <4F17D5E3.1030105@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55836 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752873Ab2ASJC3 (ORCPT ); Thu, 19 Jan 2012 04:02:29 -0500 Content-Disposition: inline In-Reply-To: <4F17D5E3.1030105@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Jan 19, 2012 at 09:35:47AM +0100, Jan Kiszka wrote: > Hi again, > > what is the best way to check if the TPR patching feature of qemu-kvm is > working and performs efficiently? I suppose Windows XP guests, e.g.? How > to measure this best? I'm about to start porting it to upstream and like > to prepare a good test case. > Run WindowsXP on AMD HW without vapic and see number of TPR access exits. Than run it with vapic and check again. Don't forget to check that reboot et al work. > Thanks, > Jan > > PS: After the /kvm removal, I'm currently counting a bit more than 7000 > LOC difference in qemu-kvm. We are converging. > > -- > Siemens AG, Corporate Technology, CT T DE IT 1 > Corporate Competence Center Embedded Linux > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Gleb.