linux-kernel - Re: [PATCH 1/6] perf, core: Add generic transaction flags v4

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: <20130916105802.GD29018@twins.programming.kicks-ass.net>
Date:	Mon, 16 Sep 2013 12:58:02 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	mingo@...nel.org, acme@...radead.org, linux-kernel@...r.kernel.org,
	eranian@...gle.com, Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 1/6] perf, core: Add generic transaction flags v4

On Fri, Sep 13, 2013 at 11:08:31AM -0700, Andi Kleen wrote:
>  /*
> + * Values for the transaction event qualifier, mostly for abort events.
> + * Multiple bits can be set.
> + */
> +enum {
> +	PERF_SAMPLE_TXN_ELISION        = (1 << 0), /* From elision */
> +	PERF_SAMPLE_TXN_TRANSACTION    = (1 << 1), /* From transaction */
> +	PERF_SAMPLE_TXN_SYNC           = (1 << 2), /* Instruction is related */
> +	PERF_SAMPLE_TXN_ASYNC          = (1 << 3), /* Instruction not related */
> +	PERF_SAMPLE_TXN_RETRY          = (1 << 4), /* Retry possible */
> +	PERF_SAMPLE_TXN_CONFLICT       = (1 << 5), /* Conflict abort */
> +	PERF_SAMPLE_TXN_CAPACITY_WRITE = (1 << 6), /* Capacity write abort */
> +	PERF_SAMPLE_TXN_CAPACITY_READ  = (1 << 7), /* Capacity read abort */
> +
> +	PERF_SAMPLE_TXN_MAX	       = (1 << 8),  /* non-ABI */
> +
> +	/* bits 24..31 are reserved for the abort code */
> +
> +	PERF_SAMPLE_TXN_ABORT_MASK  = 0xff000000,
> +	PERF_SAMPLE_TXN_ABORT_SHIFT = 24,
> +};

Why bits 24..31 ? Why not push the abort code into the upper 32 bits?
--
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/