30 Aug, 2020
2 commits
-
as they are enabled in gki_defconfig already.
Otherwise following errors will be reported when use the gki kernel:[ 3.027156] init: Loading module /lib/modules/ehci-hcd.ko with args ''
[ 3.036118] ehci_hcd: exports duplicate symbol ehci_adjust_port_wakeup_flags (owned by kernel)
[ 3.107862] init: Failed to insmod '/lib/modules/ehci-hcd.ko' with args '': Exec format error
[ 3.116546] init: LoadWithAliases was unable to load ehci_hcd
[ 3.122785] init: Failed to load kernel modules
[ 3.127938] init: InitFatalReboot: signal 6
[ 3.153428] init: #00 pc 00000000003147c8 /init (UnwindStackCurrent::UnwindFromContext(unsigned long, void*)+96)
[ 3.163815] init: #01 pc 000000000027d1e0 /init (android::init::InitFatalReboot(int)+208)
[ 3.172177] init: #02 pc 000000000027d5c8 /init (android::init::InstallRebootSignalHandlers()::$_22::__invoke(int)+32)
[ 3.183062] init: #03 pc 00000000000007f4 [vdso:0000007f8d72b000]
[ 3.189314] init: #04 pc 000000000039f1d0 /init (abort+176)
[ 3.195047] init: #05 pc 000000000028006c /init (android::init::InitAborter(char const*)+44)
[ 3.203660] init: #06 pc 00000000002d5f18 /init (android::base::SetAborter(std::__1::function&&)::$_3::__invoke(char const*)+80)
[ 3.217169] init: #07 pc 00000000002d5710 /init (android::base::LogMessage::~LogMessage()+320)
[ 3.225961] init: #08 pc 0000000000274dc8 /init (android::init::FirstStageMain(int, char**)+6072)
[ 3.235016] init: #09 pc 000000000039e190 /init (__real_libc_init(void*, void (*)(), int (*)(int, char**, char**), structors_array_t const*, bionic_tcb*)+576)Fixes: f004a66806f5 ("ANDROID: GKI: support CONFIG_USB_EHCI_HCD")
Fixes: eade9ee6fd5f ("ANDROID: GKI: support CONFIG_USB_EHCI_HCD_PLATFORM")Test: boot db845c build with android-mainline gki kernel to homescreen
Signed-off-by: Yongqin Liu
Change-Id: I202ec04aa431b9f6ff1966fb6bd50758472250e4 -
On x86, this also adds specific support for Intel and AMD versions of
the virtualization extensions. This enables running hypervisors such as
crosvm on virtualized Android guests.Bug: 165696208
Change-Id: If8c46beb16644175cce3268ed1ff083754d3cbf5
Signed-off-by: Alistair Delva
29 Aug, 2020
2 commits
-
CONFIG_V4L_MEM2MEM_DRIVERS
Bug: 165798419
Change-Id: I604ab4367714c5fc3858e1ad89504b924f8db9d2
Signed-off-by: Dmitry Shmidt -
CONFIG_ARCH_SUNXI is a dependency of sunxi devices.
Bug: 154880035
Change-Id: I476ec035f144ecc7c93f6b157779e445b16e926a
Signed-off-by: huangshuosheng
28 Aug, 2020
1 commit
-
- To use MPAM in kernel task, vendor_hook call is needed to
set MPAM at scheduling time.
- Vendor_hooks is call ed when task is switching for MPAM stateBug: 165333282
Signed-off-by: C-J.Chen
Change-Id: I30270c667c26e1a7039580b33011665bb3a8cce7
26 Aug, 2020
1 commit
-
Remove building in CONFIG_SCSI_UFS_QCOM as the in-kernel driver is quite out of
date so QCOM needs to use the out-of-tree version.Bug: 166075280
Signed-off-by: Todd Kjos
Change-Id: Ib1c4aace1553c0ab76d63e7c954ee0ff4ec144f8
25 Aug, 2020
1 commit
-
It's needed by devices, so add it to the gki defconfig files
Bug: 163109235
Bug: 163679730
Signed-off-by: Greg Kroah-Hartman
Change-Id: Ia9c77c07e7e4c590b2f82355a9db24e9bd8ab1b2
24 Aug, 2020
1 commit
-
Linux 5.9-rc2
Signed-off-by: Greg Kroah-Hartman
Change-Id: I4dd4b70b085bfa0b5cb49ffa373c18cfe857bcf3
23 Aug, 2020
2 commits
-
Pull arm64 fixes from Catalin Marinas:
- Allow booting of late secondary CPUs affected by erratum 1418040
(currently they are parked if none of the early CPUs are affected by
this erratum).- Add the 32-bit vdso Makefile to the vdso_install rule so that 'make
vdso_install' installs the 32-bit compat vdso when it is compiled.- Print a warning that untrusted guests without a CPU erratum
workaround (Cortex-A57 832075) may deadlock the affected system.* tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
ARM64: vdso32: Install vdso32 from vdso_install
KVM: arm64: Print warning when cpu erratum can cause guests to deadlock
arm64: Allow booting of late CPUs affected by erratum 1418040
arm64: Move handling of erratum 1418040 into C code -
Pull kvm fixes from Paolo Bonzini:
- PAE and PKU bugfixes for x86
- selftests fix for new binutils
- MMU notifier fix for arm64
* tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
KVM: arm64: Only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is not set
KVM: Pass MMU notifier range flags to kvm_unmap_hva_range()
kvm: x86: Toggling CR4.PKE does not load PDPTEs in PAE mode
kvm: x86: Toggling CR4.SMAP does not load PDPTEs in PAE mode
KVM: x86: fix access code passed to gva_to_gpa
selftests: kvm: Use a shorter encoding to clear RAX
22 Aug, 2020
12 commits
-
These seem to be needed by most systems, so just build them into the
kernel so we don't have to keep messing with ABI changes.Bug: 162909109
Signed-off-by: Greg Kroah-Hartman
Change-Id: I60801d9f98a37b4e84c56c0da2bf1e8d778d9953
Signed-off-by: Connor O'Brien -
UFS was not being enabled for x86 gki builds, making it hard to test
stuff locally.Also enable SCSI_UFSHCD_PCI=y so that the devices that were needing this
as a module do not need that anymore, to match up with the
SCSI_UFSHCD_PLATFORM setting.Bug: 151050916
Bug: 162909109
Signed-off-by: Greg Kroah-Hartman
Change-Id: I8af43e0a55f1467c4bd670dcdefddf3746fdd5ef
Signed-off-by: Connor O'Brien -
MEDIA_CAMERA_SUPPORT was removed from gki_defconfig in commit
b5e512c42c54 ("ANDROID: GKI: update gki defconfigs") because it is
now enabled by default unless MEDIA_SUPPORT_FILTER is enabled. After
commit 4467f1150461 ("ANDROID: gki_defconfig: Enable
MEDIA_SUPPORT_FILTER"), MEDIA_CAMERA_SUPPORT again needs to be
explicitly enabled.Bug: 162909109
Signed-off-by: Connor O'Brien
Change-Id: Ia68d6e233e86b405ea4fbc0e292e6b0778c90704 -
This enables both CONFIG_USB_STORAGE=y and CONFIG_USB_UAS=y so that
systems that want to support usb storage devices will work with the GKI
base kernel image.Bug: 161091250
Bug: 161190032
Bug: 162909109
Cc: zhang sanshan
Cc: JaeHun Jung
Signed-off-by: Greg Kroah-Hartman
Change-Id: Ibda9ad03aea3f192c057fd3e479742d52d060f7b
Signed-off-by: Connor O'Brien -
Everyone really wants either the PCI or Platform EHCI driver, so build
it in so that all boards don't have to select this as well.Based on a change from zhang sanshan.
Bug: 160193672
Bug: 162909109
Change-Id: Ie2273b5565003f339a7734f579d35b2f8bb4b0b0
Cc: zhang sanshan
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Connor O'Brien -
it use CHIPIDEA usb controller on imx8mm-evk board.
Need enable device/host mode for android device by default.
host mode depend on CONFIG_USB_CHIPIDEA_HOST which need enable CONFIG_USB_EHCI_HCD by default.
CONFIG_USB_EHCI_HCD is used for USB 2.0 "high speed" protocol.Bug: 160193672
Bug: 162909109
Change-Id: Ic635ae6c12397ed7d2060ab68fec3853fadfa6ec
Signed-off-by: zhang sanshan
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Connor O'Brien -
This is required on devices without sdcardfs.
Bug: 158733532
Bug: 162909109
Test: manual
Change-Id: I21d6ee488b7e4a094260cffc654a4c9dc3392081
Signed-off-by: Martijn Coenen
Signed-off-by: Connor O'Brien -
Enable support for devfreq driver to adjust DDR frequency.
Bug: 154672404
Bug: 162909109
Change-Id: Ic42139c54c62c6ee1bea1da002af06088e2ef268
Signed-off-by: huangshuosheng
Signed-off-by: Connor O'Brien -
These configs will now be required in aosp/1204022.
Change-Id: Ib2961a9abf545f483cd5691f04b93cffd011ec82
Signed-off-by: Siarhei Vishniakou
Bug: 136263708
Test: none
Bug: 162909109
Signed-off-by: Connor O'Brien -
When an MMU notifier call results in unmapping a range that spans multiple
PGDs, we end up calling into cond_resched_lock() when crossing a PGD boundary,
since this avoids running into RCU stalls during VM teardown. Unfortunately,
if the VM is destroyed as a result of OOM, then blocking is not permitted
and the call to the scheduler triggers the following BUG():| BUG: sleeping function called from invalid context at arch/arm64/kvm/mmu.c:394
| in_atomic(): 1, irqs_disabled(): 0, non_block: 1, pid: 36, name: oom_reaper
| INFO: lockdep is turned off.
| CPU: 3 PID: 36 Comm: oom_reaper Not tainted 5.8.0 #1
| Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015
| Call trace:
| dump_backtrace+0x0/0x284
| show_stack+0x1c/0x28
| dump_stack+0xf0/0x1a4
| ___might_sleep+0x2bc/0x2cc
| unmap_stage2_range+0x160/0x1ac
| kvm_unmap_hva_range+0x1a0/0x1c8
| kvm_mmu_notifier_invalidate_range_start+0x8c/0xf8
| __mmu_notifier_invalidate_range_start+0x218/0x31c
| mmu_notifier_invalidate_range_start_nonblock+0x78/0xb0
| __oom_reap_task_mm+0x128/0x268
| oom_reap_task+0xac/0x298
| oom_reaper+0x178/0x17c
| kthread+0x1e4/0x1fc
| ret_from_fork+0x10/0x30Use the new 'flags' argument to kvm_unmap_hva_range() to ensure that we
only reschedule if MMU_NOTIFIER_RANGE_BLOCKABLE is set in the notifier
flags.Cc:
Fixes: 8b3405e345b5 ("kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd")
Cc: Marc Zyngier
Cc: Suzuki K Poulose
Cc: James Morse
Signed-off-by: Will Deacon
Message-Id:
Signed-off-by: Paolo Bonzini -
The 'flags' field of 'struct mmu_notifier_range' is used to indicate
whether invalidate_range_{start,end}() are permitted to block. In the
case of kvm_mmu_notifier_invalidate_range_start(), this field is not
forwarded on to the architecture-specific implementation of
kvm_unmap_hva_range() and therefore the backend cannot sensibly decide
whether or not to block.Add an extra 'flags' parameter to kvm_unmap_hva_range() so that
architectures are aware as to whether or not they are permitted to block.Cc:
Cc: Marc Zyngier
Cc: Suzuki K Poulose
Cc: James Morse
Signed-off-by: Will Deacon
Message-Id:
Signed-off-by: Paolo Bonzini -
Add the 32-bit vdso Makefile to the vdso_install rule so that 'make
vdso_install' installs the 32-bit compat vdso when it is compiled.Fixes: a7f71a2c8903 ("arm64: compat: Add vDSO")
Signed-off-by: Stephen Boyd
Reviewed-by: Vincenzo Frascino
Acked-by: Will Deacon
Cc: Vincenzo Frascino
Link: https://lore.kernel.org/r/20200818014950.42492-1-swboyd@chromium.org
Signed-off-by: Catalin Marinas
21 Aug, 2020
5 commits
-
the sensor/csi/mipi driver are in drivers/media/platform/.
need enable V4L_PLATFORM_DRIVERS by default to support camera
which is need by soc vendor.Bug: 160192055
Signed-off-by: zhang sanshan
Change-Id: I38ef6c1d1dcc2101216a50ad32f7fff96fe7ea65
(cherry picked from commit 7c8a73f320ef73b7ec8d9ac87f6696ef8997436a)
[salyzyn added CONFIG_MEDIA_PLATFORM_SUPPORT as well]
Signed-off-by: Mark Salyzyn
Fixes: 06b93644f4d102bd ("media: Kconfig: add an option to filter in/out platform drivers")
Bug: 165592876 -
If guests don't have certain CPU erratum workarounds implemented, then
there is a possibility a guest can deadlock the system. IOW, only trusted
guests should be used on systems with the erratum.This is the case for Cortex-A57 erratum 832075.
Signed-off-by: Rob Herring
Acked-by: Will Deacon
Cc: Marc Zyngier
Cc: James Morse
Cc: Julien Thierry
Cc: Suzuki K Poulose
Cc: Will Deacon
Cc: kvmarm@lists.cs.columbia.edu
Link: https://lore.kernel.org/r/20200803193127.3012242-2-robh@kernel.org
Signed-off-by: Catalin Marinas -
As we can now switch from a system that isn't affected by 1418040
to a system that globally is affected, let's allow affected CPUs
to come in at a later time.Signed-off-by: Marc Zyngier
Tested-by: Sai Prakash Ranjan
Reviewed-by: Stephen Boyd
Reviewed-by: Suzuki K Poulose
Acked-by: Will Deacon
Link: https://lore.kernel.org/r/20200731173824.107480-3-maz@kernel.org
Signed-off-by: Catalin Marinas -
Instead of dealing with erratum 1418040 on each entry and exit,
let's move the handling to __switch_to() instead, which has
several advantages:- It can be applied when it matters (switching between 32 and 64
bit tasks).
- It is written in C (yay!)
- It can rely on static keys rather than alternativesSigned-off-by: Marc Zyngier
Tested-by: Sai Prakash Ranjan
Reviewed-by: Stephen Boyd
Acked-by: Will Deacon
Link: https://lore.kernel.org/r/20200731173824.107480-2-maz@kernel.org
Signed-off-by: Catalin Marinas -
Coresight driver will support to be built as Kernel module.
Disable the builtin configuration in gki_defconfig. It can
be enabled by vendor as Kernel module.Bug: 160464759
Signed-off-by: Tingwei Zhang
Change-Id: I6de8d6778703cb1db58e4343b31c06d5481b57c3
18 Aug, 2020
1 commit
-
So that the pulse8-cec driver can be enabled downstream.
Bug: 157503752
Change-Id: Icaac11d24420e0320e961d11244ea349993d5fa1
Signed-off-by: Alistair Delva
17 Aug, 2020
3 commits
-
CONFIG_MEDIA_CEC_SUPPORT
Bug: 162507365
Bug: 164180803
Change-Id: If6d4a6fbe0aebb27952c8db250db99183e211493
Signed-off-by: Dmitry Shmidt
[adelva: CONFIG_CEC_PLATFORM_DRIVERS was removed upstream]
Signed-off-by: Alistair Delva -
This reverts commit 972e02b5256aa6d40427413b2d2f19ed626156c3 because it
was a fix for commit 9cb7ec3e9be4 ("ANDROID: ASoC: core - add hostless
DAI support"), which got reverted by commit da171b5d560c ("ANDROID:
Revert "ANDROID: ASoC: core - add hostless DAI support""). Therefore
it's no longer needed.Bug: 144369166
Change-Id: If3ed9dcb04d9879d8fb4a74076c029cf8ce9a609
Signed-off-by: Eric Biggers -
…ux-block") into android-mainline
Steps on the way to 5.9-rc1
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I904678b5c31139b25fb49ee67cbacb4721a3c7bc
15 Aug, 2020
3 commits
-
Since commit 61a47c1ad3a4dc ("sysctl: Remove the sysctl system call"),
sys_sysctl is actually unavailable: any input can only return an error.We have been warning about people using the sysctl system call for years
and believe there are no more users. Even if there are users of this
interface if they have not complained or fixed their code by now they
probably are not going to, so there is no point in warning them any
longer.So completely remove sys_sysctl on all architectures.
[nixiaoming@huawei.com: s390: fix build error for sys_call_table_emu]
Link: http://lkml.kernel.org/r/20200618141426.16884-1-nixiaoming@huawei.comSigned-off-by: Xiaoming Ni
Signed-off-by: Andrew Morton
Acked-by: Will Deacon [arm/arm64]
Acked-by: "Eric W. Biederman"
Cc: Aleksa Sarai
Cc: Alexander Shishkin
Cc: Al Viro
Cc: Andi Kleen
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Arnaldo Carvalho de Melo
Cc: Arnd Bergmann
Cc: Benjamin Herrenschmidt
Cc: Bin Meng
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Catalin Marinas
Cc: chenzefeng
Cc: Christian Borntraeger
Cc: Christian Brauner
Cc: Chris Zankel
Cc: David Howells
Cc: David S. Miller
Cc: Diego Elio Pettenò
Cc: Dmitry Vyukov
Cc: Dominik Brodowski
Cc: Fenghua Yu
Cc: Geert Uytterhoeven
Cc: Heiko Carstens
Cc: Helge Deller
Cc: "H. Peter Anvin"
Cc: Ingo Molnar
Cc: Iurii Zaikin
Cc: Ivan Kokshaysky
Cc: James Bottomley
Cc: Jens Axboe
Cc: Jiri Olsa
Cc: Kars de Jong
Cc: Kees Cook
Cc: Krzysztof Kozlowski
Cc: Luis Chamberlain
Cc: Marco Elver
Cc: Mark Rutland
Cc: Martin K. Petersen
Cc: Masahiro Yamada
Cc: Matt Turner
Cc: Max Filippov
Cc: Michael Ellerman
Cc: Michal Simek
Cc: Miklos Szeredi
Cc: Minchan Kim
Cc: Namhyung Kim
Cc: Naveen N. Rao
Cc: Nick Piggin
Cc: Oleg Nesterov
Cc: Olof Johansson
Cc: Paul Burton
Cc: "Paul E. McKenney"
Cc: Paul Mackerras
Cc: Peter Zijlstra (Intel)
Cc: Randy Dunlap
Cc: Ravi Bangoria
Cc: Richard Henderson
Cc: Rich Felker
Cc: Russell King
Cc: Sami Tolvanen
Cc: Sargun Dhillon
Cc: Stephen Rothwell
Cc: Sudeep Holla
Cc: Sven Schnelle
Cc: Thiago Jung Bauermann
Cc: Thomas Bogendoerfer
Cc: Thomas Gleixner
Cc: Tony Luck
Cc: Vasily Gorbik
Cc: Vlastimil Babka
Cc: Yoshinori Sato
Cc: Zhou Yanjie
Link: http://lkml.kernel.org/r/20200616030734.87257-1-nixiaoming@huawei.com
Signed-off-by: Linus Torvalds -
Pull timekeeping updates from Thomas Gleixner:
"A set of timekeeping/VDSO updates:- Preparatory work to allow S390 to switch over to the generic VDSO
implementation.S390 requires that the VDSO data pointer is handed in to the
counter read function when time namespace support is enabled.
Adding the pointer is a NOOP for all other architectures because
the compiler is supposed to optimize that out when it is unused in
the architecture specific inline. The change also solved a similar
problem for MIPS which fortunately has time namespaces not yet
enabled.S390 needs to update clock related VDSO data independent of the
timekeeping updates. This was solved so far with yet another
sequence counter in the S390 implementation. A better solution is
to utilize the already existing VDSO sequence count for this. The
core code now exposes helper functions which allow to serialize
against the timekeeper code and against concurrent readers.S390 needs extra data for their clock readout function. The initial
common VDSO data structure did not provide a way to add that. It
now has an embedded architecture specific struct embedded which
defaults to an empty struct.Doing this now avoids tree dependencies and conflicts post rc1 and
allows all other architectures which work on generic VDSO support
to work from a common upstream base.- A trivial comment fix"
* tag 'timers-urgent-2020-08-14' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
time: Delete repeated words in comments
lib/vdso: Allow to add architecture-specific vdso data
timekeeping/vsyscall: Provide vdso_update_begin/end()
vdso/treewide: Add vdso_data pointer argument to __arch_get_hw_counter() -
Bug: 142159113
Change-Id: I89174bdba73176b017c489f4044ed90882a8f99f
Signed-off-by: Donghoon Yu
[willmcvicker: added to x86 gki_defconfig too]
Signed-off-by: Will McVicker
13 Aug, 2020
6 commits
-
rockpi4_defconfig got updated by commit 64b9a2067308 ("ANDROID: Remove
default y for VIRTIO_PCI_LEGACY"), but then the revert commit
62f596614adc ("ANDROID: Re-add default y for VIRTIO_PCI_LEGACY") forgot
to undo the change to rockpi4_defconfig. Do it now.Fixes: 62f596614adc ("ANDROID: Re-add default y for VIRTIO_PCI_LEGACY")
Change-Id: I32340f8eff6471bc6223edfbcb4071f6a235b431
Signed-off-by: Eric Biggers -
This reverts commit 588085feb44fa553aec7eb98545a570e189eabad
(change Iec9098f27c0353dabc23bd98efbca6479de41796), except
for the CONFIG_ENERGY_MODEL=y addition which is now upstream.There's no need to carry any out-of-tree changes to
arch/arm64/configs/defconfig, since Android doesn't use this.Change-Id: Icd0bf6af5d3c8b931361f36813b705f7f44f6eb0
Signed-off-by: Eric Biggers -
…ernel/git/abelloni/linux") into android-mainline
Steps on the way to 5.9-rc1.
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Iceded779988ff472863b7e1c54e22a9fa6383a30 -
Set CONFIG_LEDS_TRIGGER_TIMER=y to enable the "timer" trigger for the
LED subsystem. This creates the sysfs parameters "delay_on" and
"delay_off" for LEDs, which can then be used to specify a blinking
pattern for them.Bug: 163765274
Change-Id: I66ada688aa5026253e76588ae1d6d85eb4cd8536
Signed-off-by: Guru Das Srinagesh -
All users of arm_pm_restart() have been converted to use the kernel
restart handler.Acked-by: Arnd Bergmann
Reviewed-by: Wolfram Sang
Tested-by: Wolfram Sang
Acked-by: Catalin Marinas
Signed-off-by: Guenter Roeck
Signed-off-by: Thierry RedingBug: 163752725
Link: https://lore.kernel.org/lkml/20191015145147.1106247-6-thierry.reding@gmail.com/
Change-Id: I2c44db9cf885b9b36c8fdd82d53d9730a8cae738
Signed-off-by: Elliot Berman -
Pull more KVM updates from Paolo Bonzini:
"PPC:
- Improvements and bugfixes for secure VM support, giving reduced
startup time and memory hotplug support.- Locking fixes in nested KVM code
- Increase number of guests supported by HV KVM to 4094
- Preliminary POWER10 support
ARM:
- Split the VHE and nVHE hypervisor code bases, build the EL2 code
separately, allowing for the VHE code to now be built with
instrumentation- Level-based TLB invalidation support
- Restructure of the vcpu register storage to accomodate the NV code
- Pointer Authentication available for guests on nVHE hosts
- Simplification of the system register table parsing
- MMU cleanups and fixes
- A number of post-32bit cleanups and other fixes
MIPS:
- compilation fixesx86:
- bugfixes- support for the SERIALIZE instruction"
* tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm: (70 commits)
KVM: MIPS/VZ: Fix build error caused by 'kvm_run' cleanup
x86/kvm/hyper-v: Synic default SCONTROL MSR needs to be enabled
MIPS: KVM: Convert a fallthrough comment to fallthrough
MIPS: VZ: Only include loongson_regs.h for CPU_LOONGSON64
x86: Expose SERIALIZE for supported cpuid
KVM: x86: Don't attempt to load PDPTRs when 64-bit mode is enabled
KVM: arm64: Move S1PTW S2 fault logic out of io_mem_abort()
KVM: arm64: Don't skip cache maintenance for read-only memslots
KVM: arm64: Handle data and instruction external aborts the same way
KVM: arm64: Rename kvm_vcpu_dabt_isextabt()
KVM: arm: Add trace name for ARM_NISV
KVM: arm64: Ensure that all nVHE hyp code is in .hyp.text
KVM: arm64: Substitute RANDOMIZE_BASE for HARDEN_EL2_VECTORS
KVM: arm64: Make nVHE ASLR conditional on RANDOMIZE_BASE
KVM: PPC: Book3S HV: Rework secure mem slot dropping
KVM: PPC: Book3S HV: Move kvmppc_svm_page_out up
KVM: PPC: Book3S HV: Migrate hot plugged memory
KVM: PPC: Book3S HV: In H_SVM_INIT_DONE, migrate remaining normal-GFNs to secure-GFNs
KVM: PPC: Book3S HV: Track the state GFNs associated with secure VMs
KVM: PPC: Book3S HV: Disable page merging in H_SVM_INIT_START
...
