linux-kernel - Re: [Feature] x86_64 page tracking for Stratus servers

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, 5 Sep 2006 22:48:56 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Kimball Murray" <kimball.murray@...il.com>
Cc:	"Arjan van de Ven" <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, akpm@...eo.com
Subject: Re: [Feature] x86_64 page tracking for Stratus servers

On Tuesday 05 September 2006 20:38, Kimball Murray wrote:

> As before, Stratus would not object to providing all kernel modules as
> GPL, but still our problem is that there is some code that reflects
> some of our chipset vendor's proprietary information, so they won't

Is that Intel? They normally don't have problems with free drivers.

> At 1400 lines, I should probably find a server to make this available.
>  But not having one at the moment, please forgive the attachment.

The code would certainly need a lot of cleanup and split up etc.
(Andrew has a nice document on that somewhere, it's called "the perfect 
patch")

What I could see is that if you turn that into generic "memory mirror" 
VM code and submit the patches to do that together with some simple
that uses it. I suppose other people could then use it too and it might
end up as a nice generic facility in Linux code.

Then when that generic subsystem is in your hardware specific drivers could 
possibly use it, although it would be definitely strongly prefered if those
were GPL too.

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