linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wefu@redhat.com
To: harryxiyou@gmail.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, catalin.marinas@arm.com,
	will.deacon@arm.com, punit.agrawal@arm.com,
	suzuki.poulose@arm.com, fu.wei@linaro.org,
	Fu Wei <wefu@redhat.com>
Subject: [PATCH] Documentation:Chinese translation of Documentation/arm64/legacy_instructions.txt
Date: Wed, 25 Mar 2015 12:09:03 +0800	[thread overview]
Message-ID: <1427256543-7311-1-git-send-email-wefu@redhat.com> (raw)
In-Reply-To: <=wefu@redhat.com>

From: Fu Wei <wefu@redhat.com>

This is a Chinese translated version of Documentation/arm64/legacy_instructions.txt

It is based on the modifications of Documentation/arm64/legacy_instructions.txt in submission:
"587064b6", "bd35a4ad", "2d888f48", "c852f320".

Signed-off-by: Fu Wei <wefu@redhat.com>
---
 Documentation/zh_CN/arm64/legacy_instructions.txt | 72 +++++++++++++++++++++++
 1 file changed, 72 insertions(+)

diff --git a/Documentation/zh_CN/arm64/legacy_instructions.txt b/Documentation/zh_CN/arm64/legacy_instructions.txt
new file mode 100644
index 0000000..75b11bf
--- /dev/null
+++ b/Documentation/zh_CN/arm64/legacy_instructions.txt
@@ -0,0 +1,72 @@
+Chinese translated version of Documentation/arm64/legacy_instructions.txt
+
+If you have any comment or update to the content, please contact the
+original document maintainer directly.  However, if you have a problem
+communicating in English you can also ask the Chinese maintainer for
+help.  Contact the Chinese maintainer if this translation is outdated
+or if there is a problem with the translation.
+
+Maintainer: Punit Agrawal <punit.agrawal@arm.com>
+            Suzuki K. Poulose <suzuki.poulose@arm.com>
+Chinese maintainer: Fu Wei <wefu@redhat.com>
+---------------------------------------------------------------------
+Documentation/arm64/legacy_instructions.txt 的中文翻译
+
+如果想评论或更新本文的内容,请直接联系原文档的维护者。如果你使用英文
+交流有困难的话,也可以向中文版维护者求助。如果本翻译更新不及时或者翻
+译存在问题,请联系中文版维护者。
+
+本文翻译提交时的 Git 检出点为: bc465aa9d045feb0e13b4a8f32cc33c1943f62d6
+
+英文版维护者: Punit Agrawal <punit.agrawal@arm.com>
+            Suzuki K. Poulose <suzuki.poulose@arm.com>
+中文版维护者: 傅炜  Fu Wei <wefu@redhat.com>
+中文版翻译者: 傅炜  Fu Wei <wefu@redhat.com>
+中文版校译者: 傅炜  Fu Wei <wefu@redhat.com>
+
+以下为正文
+---------------------------------------------------------------------
+Linux 内核在 arm64 上的移植提供了一个基础框架,以支持构架中正在被淘汰或已废弃指令的模拟执行。
+这个基础框架的代码使用未定义指令钩子(hooks)来支持模拟。如果指令存在,它也允许在硬件中启用该指令。
+
+模拟模式可通过写 sysctl 节点(/proc/sys/abi)来控制。
+不同的执行方式及 sysctl 节点的相应值,解释如下:
+
+* Undef(未定义)
+  值: 0
+  产生未定义指令终止异常。它是那些构架中已废弃的指令,如 SWP,的默认处理方式。
+
+* Emulate(模拟)
+  值: 1
+  使用软件模拟方式。为解决软件迁移问题,这种模拟指令模式的使用是被跟踪的,并会发出速率限制警告。
+  它是那些构架中正在被淘汰的指令,如 CP15 barriers(隔离指令),的默认处理方式。
+
+* Hardware Execution(硬件执行)
+  值: 2
+  虽然标记为正在被淘汰,但一些实现可能提供硬件执行这些指令的使能/禁用操作。
+  使用硬件执行一般会有更好的性能,但将无法收集运行时对正被淘汰指令的使用统计数据。
+
+默认执行模式依赖于指令在构架中状态。正在被淘汰的指令应该以模拟(Emulate)作为默认模式,
+而已废弃的指令必须默认使用未定义(Undef)模式
+
+注意:指令模拟可能无法应对所有情况。更多详情请参考单独的指令注释。
+
+受支持的遗留指令
+-------------
+* SWP{B}
+节点: /proc/sys/abi/swp
+状态: 已废弃
+默认执行方式: Undef (0)
+
+* CP15 Barriers
+节点: /proc/sys/abi/cp15_barrier
+状态: 正被淘汰,不推荐使用
+默认执行方式: Emulate (1)
+
+* SETEND
+节点: /proc/sys/abi/setend
+状态: 正被淘汰,不推荐使用
+默认执行方式: Emulate (1)*
+注:为了使能这个特性,所有系统中的 CPU 必须在 EL0 支持混合字节序。
+如果一个新的 CPU (不支持混合字节序) 在使能这个特性后被热插入系统,
+该应用则可能出现不可预期的结果。
-- 
1.8.3.1


  parent reply	other threads:[~2015-03-25  4:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <=wefu@redhat.com>
2015-03-23 16:43 ` [PATCH] Documentation:Update Documentation/zh_CN/arm64/memory.txt wefu
2015-03-24  1:04   ` harryxiyou
2015-03-24  9:37 ` [PATCH] Documentation:Update Documentation/zh_CN/arm64/booting.txt wefu
2015-03-24  9:42   ` harryxiyou
2015-03-26 17:14   ` Jonathan Corbet
2015-03-25  4:09 ` wefu [this message]
2015-03-25  5:17   ` [PATCH] Documentation:Chinese translation of Documentation/arm64/legacy_instructions.txt harryxiyou
2015-03-25 15:23     ` Jonathan Corbet
2015-03-25 22:02       ` Greg-Kroah-Hartman
2015-03-26  9:46         ` Fu Wei
2015-03-26 16:23           ` Jonathan Corbet
2015-03-26  6:26   ` Amos Kong
2015-03-26  8:13     ` Fu Wei
2015-03-26  9:02 ` [PATCH v2] " wefu
2015-03-26 12:37   ` harryxiyou
2015-03-26 14:25     ` Fu Wei
2015-03-26 16:51   ` Amos Kong

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=1427256543-7311-1-git-send-email-wefu@redhat.com \
    --to=wefu@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=fu.wei@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will.deacon@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).