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: <50447442.2050307@redhat.com>
Date:	Mon, 03 Sep 2012 12:11:30 +0300
From:	Avi Kivity <avi@...hat.com>
To:	dave@....org
CC:	Marcelo Tosatti <mtosatti@...hat.com>, KVM <kvm@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] KVM: VMX: invalidate vpid for invlpg instruction

On 09/03/2012 02:27 AM, Davidlohr Bueso wrote:
> On Fri, 2012-08-31 at 14:37 -0300, Marcelo Tosatti wrote:
>> On Fri, Aug 31, 2012 at 06:10:48PM +0200, Davidlohr Bueso wrote:
>> > For processors that support VPIDs we should invalidate the page table entry
>> > specified by the lineal address. For this purpose add support for individual
>> > address invalidations.
>> 
>> Not necessary - a single context invalidation is performed through
>> KVM_REQ_TLB_FLUSH.
> 
> Since vpid_sync_context() supports both single and all-context vpid
> invalidations, wouldn't it make sense to also add individual address
> ones as well, supporting further granularity?

It might.  Do you have benchmarks supporting this?

-- 
error compiling committee.c: too many arguments to function
--
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