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]
Message-ID: <20100417191308.GA25160@elte.hu>
Date:	Sat, 17 Apr 2010 21:13:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Avi Kivity <avi@...hat.com>
Cc:	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Sheng Yang <sheng@...ux.intel.com>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	oerg Roedel <joro@...tes.org>, kvm@...r.kernel.org,
	Jes Sorensen <Jes.Sorensen@...hat.com>,
	linux-kernel@...r.kernel.org, Zachary Amsden <zamsden@...hat.com>,
	Gleb Natapov <gleb@...hat.com>, tim.c.chen@...el.com,
	zhiteng.huang@...el.com,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: [PATCH V4 1/2] perf & kvm: Enhance perf to collect KVM guest os
 statistics from host side


* Avi Kivity <avi@...hat.com> wrote:

> On 04/16/2010 10:34 AM, Zhang, Yanmin wrote:
> >Below is the kernel patch to enable perf to collect guest os statistics.
> >
> >Joerg,
> >
> >Would you like to add support on svm? I don't know the exact point to trigger
> >NMI to host with svm.
> >
> >See below code with vmx:
> >
> >+		kvm_before_handle_nmi(&vmx->vcpu);
> >  		asm("int $2");
> >+		kvm_after_handle_nmi(&vmx->vcpu);
> >
> >Signed-off-by: Zhang Yanmin<yanmin_zhang@...ux.intel.com>
> 
> Can you please split it further?
> 
> Patch 1 introduces perf_register_guest_info_callbacks() and related. Ingo 
> can merge this into a branch in tip.git. Patch 2 is just the kvm bits, I'll 
> apply that after merging the branch with patch 1. Patch 3 adds the 
> tools/perf changes.
> 
> This way perf development can continue on tip.git, and kvm development can 
> continue on kvm.git, without the code bases diverging and requiring a merge 
> later.

I'd like to pull the KVM bits from you into perf - so that there's a testable 
form of the changes. We can do that via a branch that has 1-2 changes, plus 
minimal conflicts down the line, right?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ