[0/7] updates for linux v5.2

Submitted by Szabolcs Nagy on Aug. 20, 2019, 8:17 p.m.

Details

Message ID 20190820201739.GO22009@port70.net
State New
Series "updates for linux v5.2"
Headers show

Commit Message

Szabolcs Nagy Aug. 20, 2019, 8:17 p.m.
* Rich Felker <dalias@libc.org> [2019-08-20 15:12:21 -0400]:
> We already have the first two, under BSD||GNU. Note that non-exposure
> under plain POSIX is not a choice here; AT_* is (perhaps wrongly, by
> oversight) not in the reserved namespace for fcntl.h.
> 
> I'm not sure if GNU-only is better than BSD||GNU; my leaning is
> towards keeping the latter.

ok.

> I think this is okay for now, but now that Linux has unified syscall
> numbers for all future syscalls, I wonder if we should add a
> bits/syscall_common.h or something that defines all the common ones in
> terms of some base macro, so that we don't have O(nm) growth here.

yes that would be useful.

> As before, the _OLD/_NEW names aren't needed for userspace. Rather the
> definition of the unadorned macro has to be changed from the old value
> to the new one when the time64 switchover happens (missing from the
> RFC/POC i386 commit in the "final time64 switch-over patch series"
> thread -- this needs fixing). The _OLD versions are already defined
> privately in arch/*/syscall_arch.h for 32-bit archs since commit
> 2e554617e5a6a41bf3f6c6306c753cd53abf728c, so ioctl.c can use them for
> translation.

ok.

> Also, I don't think it matters whether the _IOR macro is used or not
> since the naive switchover will require per-arch ioctl bits for all
> 32-bit archs, but maybe we can come up with a way to share some of the
> bits stuff between them and prevent introduction of new redundancy.
> Thoughts?

i see.

v2:
- AT_STATX_* are moved under _BSD_SOURCE|_GNU_SOURCE
- time_t related ioctl patch is dropped

Patch hide | download patch | download mbox

From f9a8191736c0b7e6b629b8409278887d3b0eb56f Mon Sep 17 00:00:00 2001
From: Szabolcs Nagy <nsz@port70.net>
Date: Tue, 20 Aug 2019 10:20:03 +0000
Subject: [PATCH 6/6] aarch64: add HWCAP2 flags from linux v5.2

AT_HWCAP2 flags, see

  linux commit 671db581815faf17cbedd7fcbc48823a247d90b1
  arm64: Expose DC CVADP to userspace

  linux commit 06a916feca2b262ab0c1a2aeb68882f4b1108a07
  arm64: Expose SVE2 features for userspace
---
 arch/aarch64/bits/hwcap.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/aarch64/bits/hwcap.h b/arch/aarch64/bits/hwcap.h
index ad670914..a7484028 100644
--- a/arch/aarch64/bits/hwcap.h
+++ b/arch/aarch64/bits/hwcap.h
@@ -30,3 +30,11 @@ 
 #define HWCAP_SB		(1 << 29)
 #define HWCAP_PACA		(1 << 30)
 #define HWCAP_PACG		(1UL << 31)
+
+#define HWCAP2_DCPODP		(1 << 0)
+#define HWCAP2_SVE2		(1 << 1)
+#define HWCAP2_SVEAES		(1 << 2)
+#define HWCAP2_SVEPMULL		(1 << 3)
+#define HWCAP2_SVEBITPERM	(1 << 4)
+#define HWCAP2_SVESHA3		(1 << 5)
+#define HWCAP2_SVESM4		(1 << 6)
-- 
2.21.0