linux-kernel - RE: [Xen-devel] [PATCH 0/7][v4] PV extension of HVM (Hybrid) for Xen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 2 Mar 2010 11:20:10 +0800
From:	"Dong, Eddie" <eddie.dong@...el.com>
To:	Sheng Yang <sheng@...ux.intel.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	xen-devel <xen-devel@...ts.xensource.com>,
	Ian Campbell <Ian.Campbell@...rix.com>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ian Pratt <Ian.Pratt@...citrix.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
	Keir Fraser <keir.fraser@...citrix.com>,
	"Dong, Eddie" <eddie.dong@...el.com>
Subject: RE: [Xen-devel] [PATCH 0/7][v4] PV extension of HVM (Hybrid) for Xen

> 
>> Also, I'd like to see a clearer statement of what you're specifically
>> trying to optimise for here.  What is inefficient in an unmodified
>> HVM domain, and how do your patches address these things.  What
>> measurements have you made?
> 
> The key issue we want to address is the overhead of LAPIC, especially
> EOI and other actions resulted in explicit vmexit. That is the
> overhead we want to eliminate. And evtchn seems like a perfect choice
> to us. 
> 

That is not complete. Linux timer in HVM is always annoying, and time to time make surprise to endusers. PV timer does help here. Eventchannel is nice to HVM as well. 

Thx, Eddie--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/