blocks|key|2130428|text|答案显然不是。英特尔手册，第3a卷只列出3条非特权序列化指令(cpuid、iret和rsm)，后两者似乎有控制流副作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2130429|entityMap|0|LINK|mutability|MUTABLE|url|http://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-software-developer-vol-3a-part-1-manual.html^0|V|5|11|4|16|3|7|A|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

The answer is apparently not. The <a href="http://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-software-developer-vol-3a-part-1-manual.html" rel="nofollow">Intel Manual, Volume 3a</a> lists only 3 non-privileged serializing instructions (<code>cpuid</code>, <code>iret</code>, and <code>rsm</code>), and the latter two seem to have control-flow side-effects.

blocks|key|2130435|text|你看过rdtscp指令了吗？这是rdtsc的读序列化版本。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2130436|对于基准测试，我建议阅读这张白纸。它提供了一些测量时钟滴答的最佳实践。|2130437|亚历克斯(英特尔)|2130438|entityMap|0|LINK|mutability|MUTABLE|url|http://www.intel.de/content/dam/www/public/us/en/documents/white-papers/ia-32-ia-64-benchmark-code-execution-paper.pdf^0|3|6|G|5|0|C|4|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Have you looked at the <code>rdtscp</code> instruction? This is the read serialized version of <code>rdtsc</code>. 

For benchmarking I would recommend to read <a href="http://www.intel.de/content/dam/www/public/us/en/documents/white-papers/ia-32-ia-64-benchmark-code-execution-paper.pdf">this whitepaper</a>. It provides a couple of best practices for measuring clock ticks. 

Alex(Intel)

blocks|key|1412950|text|好吧，我想这是helpfull:lfence.Ref+-《64-ia-32-architectures-software-developer-manual》第2B4-301卷|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1412951|entityMap^0|G|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Well,I guess this is helpfull:lfence.Ref this 《64-ia-32-architectures-software-developer-manual》 Vol.2B 4-301

I have seen the related question including <a href="https://stackoverflow.com/questions/2918113/cpuid-before-rdtsc">here</a> and <a href="https://stackoverflow.com/questions/12065721/why-isnt-rdtsc-a-serializing-instruction">here</a>, but it seems that the only instruction ever mentioned for serializing <code>rdtsc</code> is <code>cpuid</code>. 

Unfortunately, <code>cpuid</code> takes roughly 1000 cycles on my system, so I am wondering if anyone knows of a cheaper (fewer cycles and no read or write to memory) serializing instruction?

I looked at <code>iret</code>, but that seems to change control flow, which is also undesirable.

I have actually looked at the whitespaper linked in Alex's answer about <code>rstscp</code>, but it says:

<blockquote>
 The RDTSCP instruction waits until all previous instructions have been
 executed before reading the counter. However, subsequent
 instructions may begin execution before the read operation is
 performed.
</blockquote>

That second point seems to be make it less than ideal.

Is there a cheaper serializing instruction than cpuid?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我已经看到了包括和在内的相关问题，但似乎序列化rdtsc的唯一指令是cpuid。不幸的是，cpuid在我的系统上需要大约1000个周期，所以我想知道是否有人知道一个更便宜(周期更少，没有读或写到内存)的序列化指令？我看过iret，但这似乎改变了控制流，这也是不可取的。我实际上看过亚历克斯关于rstscp的答案中链接的白...

问是否有比cpuid更便宜的序列化指令？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否有比cpuid更便宜的序列化指令？EN