From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: akpm@linux-foundation.org, drysdale@google.com,
keescook@google.com, quentin.casasnovas@oracle.com,
sasha.levin@oracle.com, vegard.nossum@oracle.com,
linux-kernel@vger.kernel.org, edumazet@google.com,
taviso@google.com, bhelgaas@google.com,
syzkaller@googlegroups.com, kcc@google.com, glider@google.com,
ryabinin.a.a@gmail.com
Subject: Re: [PATCH v2] kernel: add kcov code coverage
Date: Thu, 14 Jan 2016 11:03:02 +0200 [thread overview]
Message-ID: <20160114090302.GA27083@node.shutemov.name> (raw)
In-Reply-To: <1452689318-107172-1-git-send-email-dvyukov@google.com>
Hi,
I've tried to build current -next with the patch. It has few reject, but
nothing major.
Booting the kernel in qemu with CONFIG_KCOV=y has failed. It hangs on
"smpboot: Total of 3 processors activated (9178.27 BogoMIPS)"
The interesting part is that I have only 2 cpu in this setup!
Huh?
CONFIG_KCOV=n works fine.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2016-01-14 9:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 12:48 [PATCH v2] kernel: add kcov code coverage Dmitry Vyukov
2016-01-13 22:31 ` kbuild test robot
2016-01-14 9:03 ` Kirill A. Shutemov [this message]
2016-01-14 9:10 ` Dmitry Vyukov
2016-01-14 9:23 ` Kirill A. Shutemov
2016-01-14 12:21 ` Dmitry Vyukov
2016-01-14 12:35 ` Kirill A. Shutemov
2016-01-14 12:49 ` Kirill A. Shutemov
2016-01-14 14:24 ` Dmitry Vyukov
2016-01-14 10:50 ` Andrey Ryabinin
2016-01-14 14:30 ` Dmitry Vyukov
2016-01-15 13:05 ` Andrey Ryabinin
2016-01-15 13:42 ` Will Deacon
2016-01-15 14:07 ` Dmitry Vyukov
2016-01-18 13:34 ` Andrey Ryabinin
2016-01-18 19:31 ` Dmitry Vyukov
2016-01-18 14:13 ` Mark Rutland
2016-01-18 19:44 ` Dmitry Vyukov
2016-01-18 20:09 ` Dmitry Vyukov
2016-01-22 11:55 ` Mark Rutland
2016-01-22 12:15 ` Dmitry Vyukov
2016-01-22 12:52 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160114090302.GA27083@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=drysdale@google.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.casasnovas@oracle.com \
--cc=ryabinin.a.a@gmail.com \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=taviso@google.com \
--cc=vegard.nossum@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox