linux-kernel - RE: [PATCH 2/9] x86: introduce a set of platform feature flags

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: <43F901BD926A4E43B106BF17856F07556428B555@orsmsx508.amr.corp.intel.com>
Date:	Thu, 2 Jul 2009 16:09:09 -0700
From:	"Pan, Jacob jun" <jacob.jun.pan@...el.com>
To:	Pavel Machek <pavel@....cz>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: RE: [PATCH 2/9] x86: introduce a set of platform feature flags

>> +#define platform_has(bit) \
>> +	test_bit(bit, (unsigned long *)platform_feature)
>
>test_bit and friends imply synchronization you probably  don't want or
>need...
>
[[JPAN]] could you explain a little more? The disassembly shows the test_bit
ends up as a testb instruction and a jump. Why there is synchronization
 involved?
Perhaps on some architectures?
--
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/