linux-kernel - RE: [patch 00/17] Text Edit Lock and Immediate Values for 2.6.25-rc8-mm1

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]

Message-ID: <002801c89adc$ec4533e0$c4cf9ba0$@css.fujitsu.com>
Date:	Thu, 10 Apr 2008 16:31:42 +0900
From:	"Takashi Nishiie" <t-nishiie@...css.fujitsu.com>
To:	<linux-kernel@...r.kernel.org>
Subject: RE: [patch 00/17] Text Edit Lock and Immediate Values for 2.6.25-rc8-mm1

Hi Mathieu

> Here is the complete patchset required to get basic Immediate Values 
> support ported to 2.6.25-rc8-mm1. It provides the "simple", non 
> nmi-safe version of immediate values, which means that immediate 
> values should not be used in code paths reachable by NMI or MCE 
> handlers. This version also uses
> stop_machine_run() for immediate values updates, which is a very heavy 
> lock.  In order to make incremental, easy to review, changes, I think 
> we could start by this "simple" version as a first step before we 
> switch to the nmi-safe version later.

I am interested in the performance improvement of "marker."
It is important in arguing that it is "simple."
I will help debug and testing.

Thanks




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