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
| ||
|
Message-ID: <20140309070642.GA2525@needle> Date: Sun, 9 Mar 2014 09:06:42 +0200 From: Muli Ben-Yehuda <muli@...technion.ac.il> To: Jon Mason <jdmason@...zu.us> Cc: "H. Peter Anvin" <hpa@...or.com>, WANG Chao <chaowang@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, Vivek Goyal <vgoyal@...hat.com>, Yinghai Lu <yinghai@...nel.org>, Baoquan He <bhe@...hat.com>, kexec@...ts.infradead.org, discuss@...-64.org, x86@...nel.org, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: How could we get rid of saved_max_pfn for calgary iommu? On Thu, Mar 06, 2014 at 07:46:44AM -0700, Jon Mason wrote: > > I don't know of anyone still using it, but it's not > > impossible. Calgary and CalIOC2 machines would now be ~5-8 years > > old. > > It is getting a bit crufty in arch/x86. Would it be better to move > it to drivers/iommu? Not sure I see the potential benefit... I think for Calgary it's either leave it in arch/x86 or rip it out. Cheers, Muli -- 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