From 41de17d4763e810edbab6f0075185dee3b92e1c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ciro=20Santilli=20=E5=85=AD=E5=9B=9B=E4=BA=8B=E4=BB=B6=20?= =?UTF-8?q?=E6=B3=95=E8=BD=AE=E5=8A=9F?= Date: Fri, 28 Jun 2019 00:00:02 +0000 Subject: [PATCH] x86 asm readme: link to LOCK answers --- README.adoc | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index ea236b2..34f1ba6 100644 --- a/README.adoc +++ b/README.adoc @@ -13128,12 +13128,17 @@ TODO We didn't manage to find a working ARM analogue to < === x86 LOCK prefix -Ensures that memory modifications are visible across all CPUs, which is fundamental for thread synchronization. - Inline assembly example at: link:userland/cpp/atomic.cpp[] +Ensures that memory modifications are visible across all CPUs, which is fundamental for thread synchronization. + Apparently already automatically implied by some of the <> +Bibliography: + +* https://stackoverflow.com/questions/8891067/what-does-the-lock-instruction-mean-in-x86-assembly/56803909#56803909 +* https://stackoverflow.com/questions/980999/what-does-multicore-assembly-language-look-like/33651438#33651438 + === x86 assembly bibliography ==== x86 official bibliography