From: Alex Shi <seakeel@gmail.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Haoyang Liu <tttturtleruss@hust.edu.cn>,
Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
Jonathan Corbet <corbet@lwn.net>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
hust-os-kernel-patches@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v3] docs/zh_CN: Add dev-tools/kcsan Chinese translation
Date: Tue, 30 Jul 2024 09:48:49 +0800 [thread overview]
Message-ID: <90b4bfb3-8fb1-4f77-b3e2-1c55605a8cbd@gmail.com> (raw)
In-Reply-To: <CAD-N9QWBH8yZcUhSLwUCZCOBrLbS1AUONik2p5E4LWYkhyVaxQ@mail.gmail.com>
On 7/30/24 9:38 AM, Dongliang Mu wrote:
>>>> "compiler instrumenting" 为什么要翻译成插桩？
>>> 指的是“KCSAN then relies on the compiler instrumenting plain accesses.”这句吗。
>> I don't understand the details of KCSAN, but according the doc, KCSAN make a array and
>> watch the data address in the array, so is there a real stub which inserted by gcc/clang?
> Yes, the compiler(gcc or clang) will insert a real stub, i.e. some
> assembly code, in the generated kernel image.
OK， then it's fine to translate like this.
next prev parent reply other threads:[~2024-07-30 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 15:08 [PATCH v3] docs/zh_CN: Add dev-tools/kcsan Chinese translation Haoyang Liu
2024-07-28 4:17 ` Alex Shi
2024-07-29 12:56 ` Haoyang Liu
2024-07-30 1:21 ` Alex Shi
2024-07-30 1:38 ` Dongliang Mu
2024-07-30 1:48 ` Alex Shi [this message]
2024-07-31 11:16 ` Haoyang Liu
2024-07-29 8:32 ` si.yanteng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90b4bfb3-8fb1-4f77-b3e2-1c55605a8cbd@gmail.com \
--to=seakeel@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=mudongliangabcd@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=siyanteng@loongson.cn \
--cc=tttturtleruss@hust.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox