linux-kernel - Re: [PATCH v3 00/24] C6X: New architecture

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:	Thu, 29 Sep 2011 08:42:37 -0400
From:	Valdis.Kletnieks@...edu
To:	Mark Salter <msalter@...hat.com>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH v3 00/24] C6X: New architecture

On Thu, 29 Sep 2011 08:21:58 EDT, Mark Salter said:

> One thing that we plan to push later is an XIP model where cores can share a
> single kernel text image but run with their own copies of data. So you end up
> with something like a loosely coupled multiprocessor system with some hardware
> support for multicore communication and peripheral sharing.

Ah, OK.  I eventually came across a mention in one of the patches of running
a separate instance of Linux on each core, whick left me even more mystified.
But the above clarifies it, thanks...

I wonder how many currently global variables will need to be moved to per_cpu
structures to make it work, and how intrusive that will end up.  Or is the plan
to have the boot loader simply plonk the entire .data/.bss in different locations
for each core?

Content of type "application/pgp-signature" skipped