From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Liang Yang" Subject: Re: [Xen-users] Does vt-x itself have perf. impact on Hypervisor w/o considering HVM? Date: Tue, 23 Jan 2007 09:15:02 -0700 Message-ID: References: <907625E08839C4409CE5768403633E0B018E18BB@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Petersson, Mats" , Xen devel list , xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Without VT-x support, binary translation has to be used to make those non-virtualizable instructions throw exception. With VT-x support, no binary translation is needed. So you mean, binary translation could be implemented as efficient as they are done in hardware? Thanks, Liang ----- Original Message ----- From: "Petersson, Mats" To: "Liang Yang" ; "Xen devel list" ; Sent: Tuesday, January 23, 2007 3:05 AM Subject: RE: [Xen-users] Does vt-x itself have perf. impact on Hypervisor w/o considering HVM? > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang > Sent: 22 January 2007 18:33 > To: Xen devel list; xen-users@lists.xensource.com > Subject: [Xen-users] Does vt-x itself have perf. impact on > Hypervisor w/o considering HVM? > > Hello, > > Suppose I have two different kinds of CPUs which have exactly > the same > configuration except one supports VT-X while the other does > not. If I want > to test the I/O performance (or other perf. testing which is not > particularly related to I/O) of the both domain0 and > Para-Virtualized Guest > Domain (HVM domain is not considered), shall I expect to get the same > performance results on these two CPUs? Assuming ALL other aspects are the same, when you're not using HVM, there should be absolutely zero impact from it (aside from it using up a few kilobytes of memory, to be precise, HVM (including both VMX and SVM) takes up 129459 bytes when not used - more memory is allocated dynamically when it's being used for obvious reasons. For modern systems, that's so small that it doesn't matter). -- Mats > > Thanks, > > Liang > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >