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]
Date:	Tue, 22 Jan 2008 14:23:55 +0100
From:	Andi Kleen <ak@...e.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <ak@...e.de>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org, jbeulich@...ell.com,
	venkatesh.pallipadi@...el.com, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: CPA boot crash (was: [PATCH] [0/36] Great change_page_attr patch series v3)

> First priority is getting CPA and PAT consolidated before we put new

PAT seems to be still quite unstable and frankly for me it is 
unclear how long it will take to it become stable. It would
not surprise me if it takes longer than the .26 merge window.

You're saying you want to delay an relatively simple and imho
relatively mature feature like gbpages after that complicated and risky 
feature PAT? Please take a look at the patches; they're really
not very complicated.

That seems to me like against your own principles -- simple stuff
first -- that you two harped on so extensively on earlier this thread.

For me it would make much more sense to put the gbpages first
than to delay them for PAT. I only didn't argue this strongly
earlier because PAT was already rushed in (for me quite suprisingly) 
and I didn't want to argue for dropping it.

But now that it is gone again anyways delaying the gbpages for it again
would be quite unfortunate from my perspective.

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