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: <20110512134339.GH8707@8bytes.org>
Date:	Thu, 12 May 2011 15:43:40 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Jan Kiszka <jan.kiszka@...mens.com>
Cc:	Avi Kivity <avi@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [PATCH v1 0/5] KVM in-guest performance monitoring

On Thu, May 12, 2011 at 03:23:39PM +0200, Jan Kiszka wrote:
> On 2011-05-12 15:11, Joerg Roedel wrote:

> > Seriously, I think such decisions should be technical only and not
> > political like that. The losers of such political decisions are always
> > the users because they don't get useful features that are technical
> > possible.
> 
> Paravirt remains a workaround, useful until hardware provides a solution
> for all guests, and that often in an even more efficient way (like for
> MMU virtualization).

Fully agreed. And todays x86 CPUs lack proper support for virtualizing
the PMU. That will hopefully change but users want the feature today.

> We do not need to block a PV-PMU for Linux guests (or other OSes that
> want to adopt to it), but that will not be a solution for the problem,
> that's my point. A PV-PMU may even be useful to demonstrate usefulness
> of a virtual PMU the CPU vendors (if they aren't aware of this yet).

Right, if users actually use the virtual PMU this probably increases the
priority for proper hardware support.

	Joerg

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