On Thu, Mar 17, 2022 at 2:40 AM Julia Lawall <julia.lawall@xxxxxxxx> wrote: > > Hello, > > The function kvm_riscv_stage2_map contains the code: > > mmu_seq = kvm->mmu_notifier_seq; > > I noticed that in every other place in the kernel where the > mmu_notifier_seq field is read, there is a read barrier after it. Is > there some reason why it is not necessary here? When I did the initial porting of KVM RISC-V (2 years back), I did not see such a barrier being used along with mmu_notifier_seq field hence the current code. I am certainly okay adding it to be consistent with other architectures. Can you send a patch for this ? Thanks, Anup > > thanks, > julia > > -- > kvm-riscv mailing list > kvm-riscv@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/kvm-riscv
