Re: [PATCH] KVM: selftests: Run dirty_log_perf_test on specific cpus

[Vipin Sharma]

On Thu, Aug 18, 2022 at 11:10 AM Sean Christopherson <seanjc@xxxxxxxxxx> wrote:
>
> On Thu, Aug 18, 2022, Vipin Sharma wrote:
> > On Wed, Aug 17, 2022 at 2:29 PM Sean Christopherson <seanjc@xxxxxxxxxx> wrote:
>
> > Okay, I will remove -d and only keep -c. I will extend it to support
> > pinning the main worker and vcpus. Arguments to -c will be like:
> > <main woker lcpu>, <vcpu0's lcpu>, <vcpu1's lcpu>, <vcpu2's lcpu>,...
> > Example:
> > ./dirty_log_perf_test -v 3 -c 1,20,21,22
> >
> > Main worker will run on 1 and 3 vcpus  will run on logical cpus 20, 21 and 22.
>
> I think it makes sense to have the vCPUs be first.  That way vcpu0 => task_map[0],
> and we can also extend the option in the future without breaking existing command
> lines, e.g. to add more workers and/or redefine the behavior of the "trailing"
> numbers to say that all workers are affined to those CPUs (to allow sequestering
> the main worker from vCPUs without pinning it to a single CPU).

Make sense. vcpus first followed by worker cpus.

Thanks