linux-kernel - Re: Basic perf PMU support for Haswell v11

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: <20130502084928.GA27847@gmail.com>
Date:	Thu, 2 May 2013 10:49:28 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...radead.org>
Subject: Re: Basic perf PMU support for Haswell v11

* Andi Kleen <andi@...stfloor.org> wrote:

> v11: Rebase to perf/core. Fix extra regs. Rename INTX.

Actually, you did not do what I asked you to do, to rename INTX to IN_TX, 
you still kept the 'INTX' pattern that is confusingly similar to 
interrupts related names like 'INT3'.

I still see, even your latest patch, this:

 +#define HSW_INTX                                       (1ULL << 32)
 +#define HSW_INTX_CHECKPOINTED                          (1ULL << 33)

Why are you ignoring maintainer requests, repeatedly?

It woulnd't be a big issue and I'd do the rename myself if this wasn't a 
repeat pattern of passive-aggressive obstruction from you spanning several 
years, resisting or obstructing maintainer feedback whenever you can ...

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/