On Tue, Sep 7, 2021 at 1:10 PM Ricardo Koller <ricarkol@xxxxxxxxxx> wrote: > > memslot_perf_test uses ucalls for synchronization between guest and > host. Ucalls API is architecture independent: tests do not need to know > details like what kind of exit they generate on a specific arch. More > specifically, there is no need to check whether an exit is KVM_EXIT_IO > in x86 for the host to know that the exit is ucall related, as > get_ucall() already makes that check. > > Change memslot_perf_test to not require specifying what exit does a > ucall generate. Also add a missing ucall_init. > > Signed-off-by: Ricardo Koller <ricarkol@xxxxxxxxxx> > --- > .../testing/selftests/kvm/memslot_perf_test.c | 56 +++++++++++-------- > 1 file changed, 34 insertions(+), 22 deletions(-) > Reviewed-by: Oliver Upton <oupton@xxxxxxxxxx> _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
