Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220819210737.763135-1-vipinsh@google.com> <YwAC1f5wTYpTdeh+@google.com>
 <CAHVum0ecr7S9QS4+3kS3Yd-eQJ5ZY_GicQWurVFnAif6oOYhOg@mail.gmail.com> <YwAP2dM/9vfjlAMb@google.com>
In-Reply-To: <YwAP2dM/9vfjlAMb@google.com>
From:   David Matlack <dmatlack@google.com>
Date:   Fri, 19 Aug 2022 15:35:07 -0700
Message-ID: <CALzav=fHWjAXthLUHJf2LdKCx1i4UO1u7iK0C6gw=y4sRw37-Q@mail.gmail.com>
Subject: Re: [PATCH v2] KVM: selftests: Run dirty_log_perf_test on specific cpus
To:     Vipin Sharma <vipinsh@google.com>
Cc:     Sean Christopherson <seanjc@google.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        kvm list <kvm@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Aug 19, 2022 at 3:34 PM David Matlack <dmatlack@google.com> wrote:
>
> On Fri, Aug 19, 2022 at 03:20:06PM -0700, Vipin Sharma wrote:
> >
> > This will assume all tests have the same pinning requirement and
> > format. What if some tests have more than one worker threads after the
> > vcpus?
>
> Even if a test has other worker threads, this proposal would still be
> logically consistent. The flag is defined to only control the vCPU
> threads and the main threads.

s/main threads/main thread/