<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/loongarch/kernel/fpu.S, branch linux-6.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-07-29T10:22:32Z</updated>
<entry>
<title>LoongArch: Re-tab the assembly files</title>
<updated>2022-07-29T10:22:32Z</updated>
<author>
<name>WANG Xuerui</name>
</author>
<published>2022-07-26T15:57:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f5c3c22f21b6a002e371afdcc9180a2fa47dc267'/>
<id>urn:sha1:f5c3c22f21b6a002e371afdcc9180a2fa47dc267</id>
<content type='text'>
Reflow the *.S files for better stylistic consistency, namely hard tabs
after mnemonic position, and vertical alignment of the first operand
with hard tabs. Tab width is obviously 8. Some pre-existing intra-block
vertical alignments are preserved.

Signed-off-by: WANG Xuerui &lt;git@xen0n.name&gt;
Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;
</content>
</entry>
<entry>
<title>LoongArch: Use the "jr" pseudo-instruction where applicable</title>
<updated>2022-07-29T10:22:32Z</updated>
<author>
<name>WANG Xuerui</name>
</author>
<published>2022-07-26T15:57:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=07b480695d24d1c9f27bb60fd4b980ae87e8bc1e'/>
<id>urn:sha1:07b480695d24d1c9f27bb60fd4b980ae87e8bc1e</id>
<content type='text'>
Some of the assembly code in the LoongArch port likely originated
from a time when the assembler did not support pseudo-instructions like
"move" or "jr", so the desugared form was used and readability suffers
(to a minor degree) as a result.

As the upstream toolchain supports these pseudo-instructions from the
beginning, migrate the existing few usages to them for better
readability.

Signed-off-by: WANG Xuerui &lt;git@xen0n.name&gt;
Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;
</content>
</entry>
<entry>
<title>LoongArch: Remove obsolete mentions of vcsr</title>
<updated>2022-07-07T09:41:01Z</updated>
<author>
<name>Qi Hu</name>
</author>
<published>2022-07-06T11:29:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=112380996ac22e428264cd7186722e784db887e4'/>
<id>urn:sha1:112380996ac22e428264cd7186722e784db887e4</id>
<content type='text'>
The `vcsr` only exists in the old hardware design, it isn't used in any
shipped hardware from Loongson-3A5000 on. Both scalar FP and LSX/LASX
instructions use the `fcsr` as their control and status registers now.
For example, the RM control bit in fcsr0 is shared by FP, LSX and LASX
instructions.

Particularly, fcsr16 to fcsr31 are reserved for LSX/LASX now, access to
these registers has no visible effect if LSX/LASX is enabled, and will
cause SXD/ASXD exceptions if LSX/LASX is not enabled.

So, mentions of vcsr are obsolete in the first place (it was just used
for debugging), let's remove them.

Reviewed-by: WANG Xuerui &lt;git@xen0n.name&gt;
Signed-off-by: Qi Hu &lt;huqi@loongson.cn&gt;
Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;
</content>
</entry>
<entry>
<title>LoongArch: Add process management</title>
<updated>2022-06-03T12:09:28Z</updated>
<author>
<name>Huacai Chen</name>
</author>
<published>2022-05-31T10:04:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=803b0fc5c3f2baa6e54978cd576407896f789b08'/>
<id>urn:sha1:803b0fc5c3f2baa6e54978cd576407896f789b08</id>
<content type='text'>
Add process management support for LoongArch, including: thread info
definition, context switch and process tracing.

Reviewed-by: WANG Xuerui &lt;git@xen0n.name&gt;
Reviewed-by: Jiaxun Yang &lt;jiaxun.yang@flygoat.com&gt;
Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;
</content>
</entry>
</feed>
