linux-kernel - RE: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state

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: <57C9024A16AD2D4C97DC78E552063EA3083291B2@orsmsx505.amr.corp.intel.com>
Date:	Mon, 4 Aug 2008 15:41:51 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	"Luck, Tony" <tony.luck@...el.com>,
	David Miller <davem@...emloft.net>
CC:	"nacc@...ibm.com" <nacc@...ibm.com>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [BISECTION RESULT] sched: revert cpu_clock to
 pre-27ec4407790d075c325e1f4da0a19c56953cce23 state

> I'm looking at that ... but it is a bit more complex.  We only have
> a "__per_cpu" block in the kernel on uni-processor systems. For
> larger systems we dynamically allocate, and we have two different
> mechanisms to that (one for SMP and one for NUMA).

Humm.  Perhaps I can always build in __per_cpu and use it for
cpu 0.  And then fix the assembly in head.S to point at that
for cpu 0.  For other cpus I's also need to pass the allocation
address of their per-cpu block to the early asm code so they
could set up ar.k3 too.

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