On Wed, Oct 23, 2019 at 3:50 PM Dmitry Vyukov wrote:
>
> On Wed, Oct 23, 2019 at 3:35 PM Andrey Konovalov
> wrote:
> >
> > On Wed, Oct 23, 2019 at 10:36 AM Dmitry Vyukov wrote:
> > >
> > > On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov
> > > wrote:
> > > >
> > > > This patch adds kcov_remot
On Wed, Oct 23, 2019 at 3:35 PM Andrey Konovalov wrote:
>
> On Wed, Oct 23, 2019 at 10:36 AM Dmitry Vyukov wrote:
> >
> > On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov
> > wrote:
> > >
> > > This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the
> > > vhost_worker() functi
On Wed, Oct 23, 2019 at 10:36 AM Dmitry Vyukov wrote:
>
> On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov
> wrote:
> >
> > This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the
> > vhost_worker() function, which is responsible for processing vhost works.
> > Since vhost_work
On Tue, Oct 22, 2019 at 6:46 PM Andrey Konovalov wrote:
>
> This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the
> vhost_worker() function, which is responsible for processing vhost works.
> Since vhost_worker() threads are spawned per vhost device instance
> the common kcov h
This patch adds kcov_remote_start()/kcov_remote_stop() annotations to the
vhost_worker() function, which is responsible for processing vhost works.
Since vhost_worker() threads are spawned per vhost device instance
the common kcov handle is used for kcov_remote_start()/stop() annotations
(see Docum
5 matches
Mail list logo