[PW_SID:1102213] RISC-V: KVM: Enhance the logging check for mmu mapping#2026
[PW_SID:1102213] RISC-V: KVM: Enhance the logging check for mmu mapping#2026linux-riscv-bot wants to merge 1 commit into
Conversation
When enabling dirty ring, the dirty bitmap is disable, and the logging check is always false as the RISC-V architecture does not select "NEED_KVM_DIRTY_RING_WITH_BITMAP". Although the dirty log is recorded since the write path already trying to add the dirty log, the logic for logging check is broken and some side effect will occurs. Enhance the logging check for mmu mapping so it can check both the dirty ring and the dirty bitmap. Signed-off-by: Inochi Amaoto <inochiama@gmail.com> Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
|
Patch 1: "RISC-V: KVM: Enhance the logging check for mmu mapping" |
2 participants
PR for series 1102213 applied to workflow__riscv__fixes
Name: RISC-V: KVM: Enhance the logging check for mmu mapping
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1102213
Version: 1