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: <19f34abd0805230830o3af93956h8152de3f6e350a09@mail.gmail.com>
Date:	Fri, 23 May 2008 17:30:55 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Pekka Enberg" <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, "Pekka Paalanen" <pq@....fi>
Subject: Re: [PATCH] kmemcheck: SMP support

On Fri, May 23, 2008 at 5:06 PM, Ingo Molnar <mingo@...e.hu> wrote:
>
> Vegard, wanna have a look at introducing per CPU kernel pagetables? I
> tried that once in the past and it wasnt too horrible. (the patches are
> gone though) We could do it before bringing other CPUs online, i.e. much
> of the really yucky boot time pagetable juggling phase would be over
> already. Hm?

Ingo.

It really doesn't matter how easy it was for you.

You're one of the x86 maintainers.

And I think you're forgetting how hard these things are for a newbie.
I don't even know which one comes first of pmds and puds.

Per-cpu page tables sounds about on the same scale of as, say,
rewriting the VM or some other major subsystem. Epic!


I'm glad to hear from you, though.

Pekka suggested that per-cpu page tables might help NUMA systems too.
Does that sound right to you? Would anybody else benefit from having
per-CPU page tables? If not, I have a hard time believing it will ever
get merged.

(Oh. mmio-trace might. But that's also a hacking tool and doesn't really count.)


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ