diff options
| author | Atish Patra <atishp@rivosinc.com> | 2025-09-09 00:03:25 -0700 |
|---|---|---|
| committer | Anup Patel <anup@brainfault.org> | 2025-09-16 11:49:31 +0530 |
| commit | 41f4d0cc331a1e9dc247ce22ae45f983f0ed9054 (patch) | |
| tree | 712b7b7ad31062b6d9f4321c793ce5e06a7a2fb7 /rust/kernel/alloc/allocator_test.rs | |
| parent | 880fcc329e2473ba02ffbc446fcd403972ab1fca (diff) | |
RISC-V: KVM: No need of explicit writable slot check
There is not much value in checking if a memslot is writable explicitly
before a write as it may change underneath after the check. Rather, return
invalid address error when write_guest fails as it checks if the slot
is writable anyways.
Suggested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Atish Patra <atishp@rivosinc.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Acked-by: Paul Walmsley <pjw@kernel.org>
Link: https://lore.kernel.org/r/20250909-pmu_event_info-v6-6-d8f80cacb884@rivosinc.com
Signed-off-by: Anup Patel <anup@brainfault.org>
Diffstat (limited to 'rust/kernel/alloc/allocator_test.rs')
0 files changed, 0 insertions, 0 deletions