<feed xmlns='http://www.w3.org/2005/Atom'>
<title>xavi/android_kernel_m2note/arch/arm64/kernel, branch o-8.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://gitea.privatedns.org/xavi/android_kernel_m2note/atom?h=o-8.1</id>
<link rel='self' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/atom?h=o-8.1'/>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/'/>
<updated>2018-11-30T13:59:28+00:00</updated>
<entry>
<title>arm64: build vdso without libgcov</title>
<updated>2018-11-30T13:59:28+00:00</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2015-11-12T14:37:12+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=1eef90798b8a428ce75b3e8fe50d363faaa42bb3'/>
<id>urn:sha1:1eef90798b8a428ce75b3e8fe50d363faaa42bb3</id>
<content type='text'>
commit 543097843ca7c9ac3758d0b5879ea2a6f44089de upstream.

On a cross-toolchain without glibc support, libgcov may not be
available, and attempting to build an arm64 kernel with GCOV
enabled then results in a build error:

/home/arnd/cross-gcc/lib/gcc/aarch64-linux/5.2.1/../../../../aarch64-linux/bin/ld: cannot find -lgcov

We don't really want to link libgcov into the vdso anyway, so
this patch just disables GCOV in the vdso directory, just as
we do for most other architectures.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Replace &lt;asm/uaccess.h&gt; with &lt;linux/uaccess.h&gt; globally</title>
<updated>2018-11-29T17:33:35+00:00</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2016-12-24T19:46:01+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=97d31ff07bb554e2861bd3e1e4ab3756a8fb1f51'/>
<id>urn:sha1:97d31ff07bb554e2861bd3e1e4ab3756a8fb1f51</id>
<content type='text'>
This was entirely automated, using the script by Al:

  PATT='^[[:blank:]]*#[[:blank:]]*include[[:blank:]]*&lt;asm/uaccess.h&gt;'
  sed -i -e "s!$PATT!#include &lt;linux/uaccess.h&gt;!" \
        $(git grep -l "$PATT"|grep -v ^include/linux/uaccess.h)

to do the replacement at the end of the merge window.

Requested-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Moyster &lt;oysterized@gmail.com&gt;
</content>
</entry>
<entry>
<title>arm64: kuser32-bit helpers: dont include unistd32.h</title>
<updated>2018-11-29T17:33:27+00:00</updated>
<author>
<name>Amit Pundir</name>
<email>amit.pundir@linaro.org</email>
</author>
<published>2015-06-24T08:51:18+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=64286824c1a388dcf3465364e1e120f579b73a65'/>
<id>urn:sha1:64286824c1a388dcf3465364e1e120f579b73a65</id>
<content type='text'>
While building lsk-3.10-android branch, we run into a series
of build warnings for arm64 arch:
----------
In file included from arch/arm64/kernel/kuser32.S:32:0:
arch/arm64/include/asm/unistd32.h:24:0: warning: "__NR_restart_syscall" redefined
 #define __NR_restart_syscall 0
 ^
In file included from include/asm-generic/unistd.h:1:0,
                 from arch/arm64/include/uapi/asm/unistd.h:16,
                 from arch/arm64/include/asm/unistd.h:50,
                 from arch/arm64/kernel/kuser32.S:31:
include/uapi/asm-generic/unistd.h:390:0: note: this is the location of the previous definition
 #define __NR_restart_syscall 128
 ^
In file included from arch/arm64/kernel/kuser32.S:32:0:
arch/arm64/include/asm/unistd32.h:26:0: warning: "__NR_exit" redefined
 #define __NR_exit 1
 ^
In file included from include/asm-generic/unistd.h:1:0,
                 from arch/arm64/include/uapi/asm/unistd.h:16,
                 from arch/arm64/include/asm/unistd.h:50,
                 from arch/arm64/kernel/kuser32.S:31:
include/uapi/asm-generic/unistd.h:292:0: note: this is the location of the previous definition
 #define __NR_exit 93
 ^
----------

This fix removes asm/unitstd32.h include to avoid duplication of
"__NR_" syscall definitions. It is based on mainline commit:
f3e5c847ec3d "arm64: Add __NR_* definitions for compat syscalls".

The corresponding change in AOSP (commit: cfc7e99e9e39, "arm64: Add..")
seem to be the early version or backport of the above mainline
commit to aosp/android-3.10. The only difference between mainline and
aosp commit is that the latter didn't have to deal with that
problematic include because it is not present in aosp/android-3.10
unlike mainline or lsk-v3.10-android tree.

Signed-off-by: Amit Pundir &lt;amit.pundir@linaro.org&gt;
Signed-off-by: Kevin Hilman &lt;khilman@linaro.org&gt;
</content>
</entry>
<entry>
<title>arm64: issue isb when trapping CNTVCT_EL0 access</title>
<updated>2018-01-15T21:50:06+00:00</updated>
<author>
<name>Greg Hackmann</name>
<email>ghackmann@google.com</email>
</author>
<published>2017-10-04T16:31:34+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=35498f0865c32babf5cc07f9a8a8d979f3949ab7'/>
<id>urn:sha1:35498f0865c32babf5cc07f9a8a8d979f3949ab7</id>
<content type='text'>
Bug: 68266545
Change-Id: I6005a6e944494257bfc2243fde2f7a09c3fd76c6
</content>
</entry>
<entry>
<title>BACKPORT: arm64: Add CNTFRQ_EL0 trap handler</title>
<updated>2018-01-15T21:50:00+00:00</updated>
<author>
<name>Marc Zyngier</name>
<email>marc.zyngier@arm.com</email>
</author>
<published>2017-04-24T08:04:03+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=7fc6c7226cd8346fae413ebe898789f321e86852'/>
<id>urn:sha1:7fc6c7226cd8346fae413ebe898789f321e86852</id>
<content type='text'>
We now trap accesses to CNTVCT_EL0 when the counter is broken
enough to require the kernel to mediate the access. But it
turns out that some existing userspace (such as OpenMPI) do
probe for the counter frequency, leading to an UNDEF exception
as CNTVCT_EL0 and CNTFRQ_EL0 share the same control bit.

The fix is to handle the exception the same way we do for CNTVCT_EL0.

Bug: 68266545
Fixes: a86bd139f2ae ("arm64: arch_timer: Enable CNTVCT_EL0 trap if workaround is enabled")
Reported-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;
Tested-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;
Reviewed-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;
Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt;
Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
(cherry picked from commit 9842119a238bfb92cbab63258dabb54f0e7b111b)

Change-Id: Ie5a9a93fcca238d6097ecacd6df0e540be90220b
</content>
</entry>
<entry>
<title>BACKPORT: arm64: Add CNTVCT_EL0 trap handler</title>
<updated>2018-01-15T21:49:56+00:00</updated>
<author>
<name>Marc Zyngier</name>
<email>marc.zyngier@arm.com</email>
</author>
<published>2017-02-01T11:48:58+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=2d6dba834d9d3fc3654d0cd647dc033ba6821721'/>
<id>urn:sha1:2d6dba834d9d3fc3654d0cd647dc033ba6821721</id>
<content type='text'>
Since people seem to make a point in breaking the userspace visible
counter, we have no choice but to trap the access. Add the required
handler.

Bug: 68266545
Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Acked-by: Mark Rutland &lt;mark.rutland@arm.com&gt;
Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt;
(cherry picked from commit 6126ce0588eb5a0752d5c8b5796a7fca324fd887)

Change-Id: I0705f47c85a78040df38df18f51a4a22500b904d
</content>
</entry>
<entry>
<title>UPSTREAM: arm64: jump labels: NOP out NOP -&gt; NOP replacement</title>
<updated>2017-12-25T15:47:53+00:00</updated>
<author>
<name>Mark Rutland</name>
<email>mark.rutland@arm.com</email>
</author>
<published>2014-11-25T15:44:18+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=9ac742112ef23ef58febf05127c0f6c8cff508d2'/>
<id>urn:sha1:9ac742112ef23ef58febf05127c0f6c8cff508d2</id>
<content type='text'>
In the arm64 arch_static_branch implementation we place an A64 NOP into
the instruction stream and log relevant details to a jump_entry in a
__jump_table section. Later this may be replaced with an immediate
branch without link to the code for the unlikely case.

At init time, the core calls arch_jump_label_transform_static to
initialise the NOPs. On x86 this involves inserting the optimal NOP for
a given microarchitecture, but on arm64 we only use the architectural
NOP, and hence replace each NOP with the exact same NOP. This is
somewhat pointless.

Additionally, at module load time we don't call jump_label_apply_nops to
patch the optimal NOPs in, unlike other architectures, but get away with
this because we only use the architectural NOP anyway. A later notifier
will patch NOPs with branches as required.

Similarly to x86 commit 11570da1c5b1dee1 (x86/jump-label: Do not bother
updating NOPs if they are correct), we can avoid patching NOPs with
identical NOPs. Given that we only use a single NOP encoding, this means
we can NOP-out the body of arch_jump_label_transform_static entirely. As
the default __weak arch_jump_label_transform_static implementation
performs a patch, we must use an empty function to achieve this.

Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;
Cc: Jiang Liu &lt;liuj97@gmail.com&gt;
Cc: Laura Abbott &lt;lauraa@codeaurora.org&gt;
Acked-by: Will Deacon &lt;will.deacon@arm.com&gt;
Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;
Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt;

(cherry picked from commit 6ddae4186886a81e22ad78ad7c6936ed36bc8225)
Signed-off-by: Tomasz Figa &lt;tfiga@chromium.org&gt;

Bug: 24475017

Change-Id: I9ef07c3a5a7f91418b30006850fcc0c421e147e2
Signed-off-by: Kees Cook &lt;keescook@google.com&gt;
Signed-off-by: franciscofranco &lt;franciscofranco.1990@gmail.com&gt;
Signed-off-by: Joe Maples &lt;joe@frap129.org&gt;
</content>
</entry>
<entry>
<title>arm64: use the new *_relaxed macros for lower power usage</title>
<updated>2017-12-25T15:47:53+00:00</updated>
<author>
<name>franciscofranco</name>
<email>franciscofranco.1990@gmail.com</email>
</author>
<published>2015-12-05T04:01:17+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=f838c93f4397015d72a92e3af19e3c2563938d3c'/>
<id>urn:sha1:f838c93f4397015d72a92e3af19e3c2563938d3c</id>
<content type='text'>
Signed-off-by: franciscofranco &lt;franciscofranco.1990@gmail.com&gt;
Signed-off-by: Joe Maples &lt;joe@frap129.org&gt;
Signed-off-by: Mister Oyster &lt;oysterized@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "arch/arm64: skip randomization within stack"</title>
<updated>2017-12-22T15:24:42+00:00</updated>
<author>
<name>Mister Oyster</name>
<email>oysterized@gmail.com</email>
</author>
<published>2017-12-21T20:12:20+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=a16d2b6a00a23a75a41e189a0da4fb56f62e6833'/>
<id>urn:sha1:a16d2b6a00a23a75a41e189a0da4fb56f62e6833</id>
<content type='text'>
This reverts commit 76848d1b0190a973e54cde8b7dab8af87b34f6f5.
</content>
</entry>
<entry>
<title>log: Initial dmesg pruning</title>
<updated>2017-12-18T22:29:17+00:00</updated>
<author>
<name>Nathan Chancellor</name>
<email>natechancellor@gmail.com</email>
</author>
<published>2017-02-23T01:46:16+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/android_kernel_m2note/commit/?id=92a746059b8ea3067f591249835d94366ab51e2d'/>
<id>urn:sha1:92a746059b8ea3067f591249835d94366ab51e2d</id>
<content type='text'>
These are all of the annoying messages on just the stock kernel...

More to follow in future patches!

Signed-off-by: Nathan Chancellor &lt;natechancellor@gmail.com&gt;
Signed-off-by: Mister Oyster &lt;oysterized@gmail.com&gt;
</content>
</entry>
</feed>
