linux-kernel - Re: [PATCH 0/3] perf_event: enable overflow interrupts on KNC

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: <20121018185437.GA21109@gmail.com>
Date:	Thu, 18 Oct 2012 20:54:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	eranian@...il.com,
	"Meadows, Lawrence F" <lawrence.f.meadows@...el.com>
Subject: Re: [PATCH 0/3] perf_event: enable overflow interrupts on KNC


* Vince Weaver <vincent.weaver@...ne.edu> wrote:

> I looked into getting a 3.7 kernel up and going on the KNC 
> board, but the diff between Intel's release and stock 
> 2.6.34.11 has 70k lines.  Much of that is kdb, but there's 
> also a lot of low-level changes too, some of it due to the 
> fact that KNC is 64-bit x86 but has no support for SSE (so you 
> need to handle that properly or none of your userspace will 
> run).

Getting that support upstream would definitely be useful, so if 
you feel so inclined splitting out (or creating anew) the 
required patches ...

I don't know how it's structured, but making the !SSE 
distinction runtime would be strongly preferred over any 
compile-time .config switchery. Otherwise, the guiding principle 
is that we'll do whatever it takes to support the hardware, with 
the reasonably best possible cleanliness.

Thanks,

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