在嵌入式系统中，周界锁定主要是什么？
我不断听到“周界锁定”以及其他主题，例如“竞争条件、IPC ..” - “周界锁定”是什么意思？任何指针或链接也会有帮助。我看到它在“工作要求”下被提及，例如“理解 DMA 引擎、中断、定时器、内存虚拟化、竞争条件和周边锁定的概念......”我 认识其他人，但不认识“周界锁定”。
谢谢
I keep hearing "perimeter locking" along with other topics such as "race conditions, IPC .." - what does "perimeter locking" mean? any pointers or links will be helpful too. I see it being referred to under "Job Requirements" such as " understanding concepts of DMA engines, interrupts, timers, memory virtualization, race conditions, and perimeter locking..." I
recognize others but not "perimeter locking".
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
可能是“不要让 JTAG/ISP 连接器可访问”之类的事情。对于普通 PC，它显然还包括火线端口，该端口可以（滥用）用于执行有趣的操作，例如访问 PC 的内存，而无需在其上运行特殊软件。
Probably things like "do not leave a JTAG/ISP connector accessible". For a regular PC it would clearly also include the firewire port which can be (ab)used to do interesting things like accessing the PC's memory without running special software on it.
这是我知道嵌入式系统软件环境中“周界锁”用法的一个实例。
假设一个嵌入式系统软件模块公开多个 API。根据设计，该模块要求每个 API 在执行时是互斥的。这通常是通过使用“互斥体”来保护 API 的入口和出口来实现的。该互斥锁被称为“周边锁”。
This is one instance where I'm aware of 'perimeter lock' usage in embedded systems software context.
Assume an embedded system software module which exposes multiple APIs. By design, the module require each of those API to be mutually exclusive in execution. This is generally achieved by using a 'mutex' to guard the entry-exit of the APIs. This mutex is referred as 'perimeter lock'.