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] [day] [month] [year] [list]
Message-ID: <1267175072.11737.11908.camel@zakaz.uk.xensource.com>
Date:	Fri, 26 Feb 2010 09:04:32 +0000
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	"akataria@...are.com" <akataria@...are.com>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: VMI and kmap_atomic_pte paravirt_op

On Thu, 2010-02-25 at 20:32 +0000, Alok Kataria wrote:
> Hi Ian, 
> 
> On Thu, 2010-02-25 at 11:52 -0800, Ian Campbell wrote:
> > Hi Alok,
> > 
> > How critical is the vmi_kmap_atomic_pte pv_mmu_op hook to VMI? Is it
> > required for correct functionality or is it simply an optimisation?
> > 
> > We think we may be able to do away with the Xen version of the hook and
> > if VMI (which is deprecated) can live without it and you agree then I'll
> > cook up a patch to remove it altogether.
> 
> As Jeremy suggests we will be fine with disabling high ptes for VMI. 
> Thanks for doing this. 

OK, I'll do that.

Thanks,
Ian.


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