messages from 2022-11-13 16:38:53 to 2022-11-18 12:20:02 UTC [more...]
[PATCH v3 0/2] KVM: arm64: Fixes for parallel faults series
2022-11-18 12:19 UTC (12+ messages)
` [PATCH v3 1/2] KVM: arm64: Take a pointer to walker data in kvm_dereference_pteref()
` [PATCH v3 2/2] KVM: arm64: Don't acquire RCU read lock for exclusive table walks
[PATCH v4 00/16] KVM: arm64: PMU: Fixing chained events, and PMUv3p5 support
2022-11-18 7:45 UTC (35+ messages)
` [PATCH v4 01/16] arm64: Add ID_DFR0_EL1.PerfMon values for PMUv3p7 and IMP_DEF
` [PATCH v4 02/16] KVM: arm64: PMU: Align chained counter implementation with architecture pseudocode
` [PATCH v4 03/16] KVM: arm64: PMU: Always advertise the CHAIN event
` [PATCH v4 04/16] KVM: arm64: PMU: Distinguish between 64bit counter and 64bit overflow
` [PATCH v4 05/16] KVM: arm64: PMU: Narrow the overflow checking when required
` [PATCH v4 06/16] KVM: arm64: PMU: Only narrow counters that are not 64bit wide
` [PATCH v4 07/16] KVM: arm64: PMU: Add counter_index_to_*reg() helpers
` [PATCH v4 08/16] KVM: arm64: PMU: Simplify setting a counter to a specific value
` [PATCH v4 09/16] KVM: arm64: PMU: Do not let AArch32 change the counters' top 32 bits
` [PATCH v4 10/16] KVM: arm64: PMU: Move the ID_AA64DFR0_EL1.PMUver limit to VM creation
` [PATCH v4 11/16] KVM: arm64: PMU: Allow ID_AA64DFR0_EL1.PMUver to be set from userspace
` [PATCH v4 12/16] KVM: arm64: PMU: Allow ID_DFR0_EL1.PerfMon "
` [PATCH v4 13/16] KVM: arm64: PMU: Implement PMUv3p5 long counter support
` [PATCH v4 14/16] KVM: arm64: PMU: Allow PMUv3p5 to be exposed to the guest
` [PATCH v4 15/16] KVM: arm64: PMU: Simplify vcpu computation on perf overflow notification
` [PATCH v4 16/16] KVM: arm64: PMU: Make kvm_pmc the main data structure
[PATCH v2] KVM: arm64: Update comment of create_hyp_mappings
2022-11-18 5:59 UTC
[PATCH 00/14] KVM: Halt-polling fixes, cleanups and a new stat
2022-11-18 2:29 UTC (10+ messages)
` disabling halt polling broken? (was Re: [PATCH 00/14] KVM: Halt-polling fixes, cleanups and a new stat)
[v2 0/6] KVM: arm64: implement vcpu_is_preempted check
2022-11-18 0:20 UTC (4+ messages)
` [External] "
[PATCH 0/2] KVM: arm64: selftests: Fixes for single-step test
2022-11-17 22:32 UTC (22+ messages)
` [PATCH 1/2] KVM: arm64: selftests: Disable single-step with correct KVM define
` [PATCH 2/2] KVM: arm64: selftests: Disable single-step without relying on ucall()
[RFC PATCH 00/12] KVM: arm64: Eager huge-page splitting for dirty-logging
2022-11-17 21:50 UTC (23+ messages)
` [RFC PATCH 01/12] KVM: arm64: Relax WARN check in stage2_make_pte()
` [RFC PATCH 02/12] KVM: arm64: Allow visiting block PTEs in post-order
` [RFC PATCH 04/12] KVM: arm64: Add kvm_pgtable_stage2_split()
` [RFC PATCH 06/12] KVM: arm64: Split block PTEs without using break-before-make
[PATCH 00/44] KVM: Rework kvm_init() and hardware enabling
2022-11-17 15:16 UTC (31+ messages)
` [PATCH 10/44] KVM: VMX: Clean up eVMCS enabling if KVM initialization fails
` [PATCH 13/44] KVM: x86: Serialize vendor module initialization (hardware setup)
` [PATCH 33/44] KVM: x86: Do VMX/SVM support checks directly in vendor code
` [PATCH 38/44] KVM: Disable CPU hotplug during hardware enabling
[PATCH v3 0/8] perf: Arm SPEv1.2 support
2022-11-17 14:43 UTC (3+ messages)
[PATCH 00/12] KVM: arm64: FF-A proxy for pKVM
2022-11-16 17:48 UTC (32+ messages)
` [PATCH 01/12] firmware: arm_ffa: Move constants to header file
` [PATCH 02/12] firmware: arm_ffa: Move comment before the field it is documenting
` [PATCH 03/12] KVM: arm64: Block unsafe FF-A calls from the host
` [PATCH 04/12] KVM: arm64: Probe FF-A version and host/hyp partition ID during init
` [PATCH 05/12] KVM: arm64: Handle FFA_FEATURES call from the host
` [PATCH 06/12] KVM: arm64: Allocate pages for hypervisor FF-A mailboxes
` [PATCH 07/12] KVM: arm64: Handle FFA_RXTX_MAP and FFA_RXTX_UNMAP calls from the host
` [PATCH 08/12] KVM: arm64: Add FF-A helpers to share/unshare memory with secure world
` [PATCH 09/12] KVM: arm64: Handle FFA_MEM_SHARE calls from the host
` [PATCH 10/12] KVM: arm64: Handle FFA_MEM_RECLAIM "
` [PATCH 11/12] KVM: arm64: Handle FFA_MEM_LEND "
` [PATCH 12/12] ANDROID: KVM: arm64: pkvm: Add support for fragmented FF-A descriptors
[PATCH] KVM: arm64: Update comment of create_hyp_mappings
2022-11-16 9:48 UTC (3+ messages)
[PATCH v2] KVM: arm64: Don't acquire RCU read lock for exclusive table walks
2022-11-16 8:14 UTC (8+ messages)
[PATCH v5 00/14] KVM: arm64: Parallel stage-2 fault handling
2022-11-15 18:57 UTC (12+ messages)
` [PATCH v5 08/14] KVM: arm64: Protect stage-2 traversal with RCU
[PATCH 0/1] KVM: arm64: Skip RCU protection for hyp stage-1
2022-11-15 17:23 UTC (8+ messages)
` [PATCH 1/1] KVM: arm64: Use a separate function for hyp stage-1 walks
[PATCH v5 0/8] arm64/sve: Clean up KVM integration and optimise syscalls
2022-11-15 9:46 UTC (9+ messages)
` [PATCH v5 1/8] KVM: arm64: Discard any SVE state when entering KVM guests
` [PATCH v5 2/8] arm64/fpsimd: Track the saved FPSIMD state type separately to TIF_SVE
` [PATCH v5 3/8] arm64/fpsimd: Have KVM explicitly say which FP registers to save
` [PATCH v5 4/8] arm64/fpsimd: Stop using TIF_SVE to manage register saving in KVM
` [PATCH v5 5/8] arm64/fpsimd: Load FP state based on recorded data type
` [PATCH v5 6/8] arm64/fpsimd: SME no longer requires SVE register state
` [PATCH v5 7/8] arm64/sve: Leave SVE enabled on syscall if we don't context switch
` [PATCH v5 8/8] arm64/fp: Use a struct to pass data to fpsimd_bind_state_to_cpu()
[PATCH 0/2] KVM: selftests: Enable access_tracking_perf_test for arm64
2022-11-14 21:57 UTC (6+ messages)
` [PATCH 1/2] KVM: selftests: Allow >1 guest mode in access_tracking_perf_test
[PATCH v6 00/26] KVM: arm64: Introduce pKVM hyp VM and vCPU state at EL2
2022-11-14 19:30 UTC (6+ messages)
[RFC PATCH 0/3] KVM: arm64: Allow userspace to trap hypercall ranges
2022-11-14 11:36 UTC (8+ messages)
` [RFC PATCH 2/3] KVM: arm64: Allow userspace to trap SMCCC sub-ranges
[PATCH v4 0/8] arm64/sve: Clean up KVM integration and optimise syscalls
2022-11-14 11:25 UTC (19+ messages)
` [PATCH v4 1/8] KVM: arm64: Discard any SVE state when entering KVM guests
` [PATCH v4 2/8] arm64/fpsimd: Track the saved FPSIMD state type separately to TIF_SVE
` [PATCH v4 3/8] arm64/fpsimd: Have KVM explicitly say which FP registers to save
` [PATCH v4 4/8] arm64/fpsimd: Stop using TIF_SVE to manage register saving in KVM
` [PATCH v4 5/8] arm64/fpsimd: Load FP state based on recorded data type
` [PATCH v4 6/8] arm64/fpsimd: SME no longer requires SVE register state
` [PATCH v4 7/8] arm64/sve: Leave SVE enabled on syscall if we don't context switch
` [PATCH v4 8/8] arm64/fp: Use a struct to pass data to fpsimd_bind_state_to_cpu()
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox