* Avi Kivity <[EMAIL PROTECTED]> wrote:
> Looks like a lot of complexity for very little gain. I'm not sure
> what the vmwrite cost is, cut it can't be that high compared to
> vmexit.
while i disagree with characterising one extra parameter passed down
plus one extra branch as 'a lot of complexity', i agree that making the
flush a NOP on VMX is even better. (if it's possible without breaking
future hardware) I guess you are right that the only true cost here is
the vmwrite cost, and that there's no impact on CR3 flushing (because it
happens unconditionally). Forget about this patch.
Ingo
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
