| author | Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de> | |
| Fri, 26 Jan 2018 09:43:24 +0000 (10:43 +0100) | ||
| committer | Jan Kiszka <jan.kiszka@siemens.com> | |
| Fri, 26 Jan 2018 17:17:55 +0000 (18:17 +0100) | ||
| commit | 9f4a52b276f2fec01bef186ce2df1e28bfc925d9 | |
| tree | 4bc3417152f16388566de9a7b9cd569832f0a6dd | tree | snapshot (tar.xz tar.gz zip) |
| parent | 0a9e81d93de37733d5970280a20aae63b0ea21ba | commit | diff |
core: arm: provide correct sender ID when reinjecting SGIs
When receiving a SGI, GICv2 provides some bits for the sender ID. Fill
them correctly.
Most OSes disregard those bits, so this wasn't noticed yet.
Nevertheless, this should be implemented in order to stick to the GICv2
specification.
GICv3 does not reinject sender IDs.
Signed-off-by: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
When receiving a SGI, GICv2 provides some bits for the sender ID. Fill
them correctly.
Most OSes disregard those bits, so this wasn't noticed yet.
Nevertheless, this should be implemented in order to stick to the GICv2
specification.
GICv3 does not reinject sender IDs.
Signed-off-by: Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>