[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 2/3] KVM: keep track of running ioctls
|
From: |
Robert Hoo |
|
Subject: |
Re: [PATCH v3 2/3] KVM: keep track of running ioctls |
|
Date: |
Fri, 02 Dec 2022 21:32:01 +0800 |
On Fri, 2022-12-02 at 13:03 +0100, Emanuele Giuseppe Esposito wrote:
...
> > > @@ -3032,7 +3035,9 @@ int kvm_vcpu_ioctl(CPUState *cpu, int type,
> > > ...)
> > > va_end(ap);
> > >
> > > trace_kvm_vcpu_ioctl(cpu->cpu_index, type, arg);
> > > + accel_cpu_ioctl_begin(cpu);
> >
> > Does this mean that kvm_region_commit() can inhibit any other vcpus
> > doing any ioctls?
>
> Yes, because we must prevent any vcpu from reading memslots while we
> are
> updating them.
>
But do most other vm/vcpu ioctls contend with memslot operations?