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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 10 Mar 2014 22:20:45 -0700
From:	Jon Mason <>
To:	Muli Ben-Yehuda <>
Cc:	"H. Peter Anvin" <>, WANG Chao <>,
	Thomas Gleixner <>,
	Vivek Goyal <>,
	Yinghai Lu <>, Baoquan He <>,,,,
	linux-kernel <>
Subject: Re: How could we get rid of saved_max_pfn for calgary iommu?

On Sun, Mar 9, 2014 at 12:06 AM, Muli Ben-Yehuda <> wrote:
> 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.

The intent is for it go where the other IOMMU drivers are, and gain
changes to the overall infrastructure as it evolves.  There has been a
decent amount of work going on in there  :)

Of course, someone would have to put the effort in and test it.

> Cheers,
> Muli
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists