linux-kernel - Re: [PATCH 2/2] Dirty page tracking & on-the-fly memory mirroring

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:	Sat, 1 Aug 2009 11:52:27 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jim Paradis <jparadis@...hat.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] Dirty page tracking & on-the-fly memory mirroring

On Fri, Jul 31, 2009 at 09:01:13PM -0400, Jim Paradis wrote:
>
> This patch is a reference implementation of a memory-mirroring module
> ("pagesync").  It is the same code that Stratus uses minus some
> hardware-specific bits.  This module scans through physical memory,
> clearing the hardware dirty bit of any dirty page and setting the
> software dirty bit.  If a dirty page has the *hardware* dirty bit
> set on a subsequent scan, we know that the page has been re-dirtied
> and it is a candidate for being copied again.

As mentioned in the prevois mail example code is uttely useless.  Please
post the real code for the stratus hardware, and also make in built-in
instead of opening big holes for external propritary modules.
--
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/