linux-kernel - [PATCH 0/5] Rework of msrpm optimization and additional fixes for nested svm

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-next>] [day] [month] [year] [list]

Message-ID: <1267118149-15737-1-git-send-email-joerg.roedel@amd.com>
Date:	Thu, 25 Feb 2010 18:15:44 +0100
From:	Joerg Roedel <joerg.roedel@....com>
To:	Avi Kivity <avi@...hat.com>, Marcelo Tosatti <mtosatti@...hat.com>
CC:	Alexander Graf <agraf@...e.de>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] Rework of msrpm optimization and additional fixes for nested svm

Hi,

this is the updated version of the msrpm merge optimization in the nested vmrun
path. With nested-shadow I see a performance improvement by a factor of two in
an up guest with kernel compile times.
A few other fixes are also included like the iopm check for nested io
intercepts and the masking of lower 12 bits of the msrpm address supplied in
the nested vmcb.
Please review and/or apply these changes.

	Joerg

diffstat:

 arch/x86/kvm/svm.c |  187 +++++++++++++++++++++++++++++++++++++---------------
 1 files changed, 133 insertions(+), 54 deletions(-)

shortlog:

Joerg Roedel (5):
      KVM: SVM: Move msrpm offset calculation to seperate function
      KVM: SVM: Optimize nested svm msrpm merging
      KVM: SVM: Use svm_msrpm_offset in nested_svm_exit_handled_msr
      KVM: SVM: Add correct handling of nested iopm
      KVM: SVM: Ignore lower 12 bit of nested msrpm_pa


--
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/