On Tue, Apr 12, 2016 at 01:17:00PM +0200, Alexander Potapenko wrote:
> On Mon, Apr 4, 2016 at 7:30 PM, Dmitry Vyukov wrote:
> > I did not look at all boot crashes and hangs. The low level arch code
> > like interrupts and early bootstrap is not interesting in this
> > setting,
On Tue, Apr 12, 2016 at 01:17:00PM +0200, Alexander Potapenko wrote:
> On Mon, Apr 4, 2016 at 7:30 PM, Dmitry Vyukov wrote:
> > I did not look at all boot crashes and hangs. The low level arch code
> > like interrupts and early bootstrap is not interesting in this
> > setting, so I just bisected
Hi James,
On Wed, Apr 13, 2016 at 6:12 PM, James Morse wrote:
> Hi Alex,
>
> On 12/04/16 12:17, Alexander Potapenko wrote:
>> I also wonder if we can, say, land the change to arch/arm64/Kconfig
>> separately from makefile changes that improve the precision or fix
>> certain
Hi James,
On Wed, Apr 13, 2016 at 6:12 PM, James Morse wrote:
> Hi Alex,
>
> On 12/04/16 12:17, Alexander Potapenko wrote:
>> I also wonder if we can, say, land the change to arch/arm64/Kconfig
>> separately from makefile changes that improve the precision or fix
>> certain build configurations.
Hi Alex,
On 12/04/16 12:17, Alexander Potapenko wrote:
> I also wonder if we can, say, land the change to arch/arm64/Kconfig
> separately from makefile changes that improve the precision or fix
> certain build configurations.
(I'm not sure what you mean by precision)
It depends which build
Hi Alex,
On 12/04/16 12:17, Alexander Potapenko wrote:
> I also wonder if we can, say, land the change to arch/arm64/Kconfig
> separately from makefile changes that improve the precision or fix
> certain build configurations.
(I'm not sure what you mean by precision)
It depends which build
On Mon, Apr 4, 2016 at 7:30 PM, Dmitry Vyukov wrote:
> On Thu, Mar 31, 2016 at 7:18 PM, Alexander Potapenko
> wrote:
>> On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
>>> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander
On Mon, Apr 4, 2016 at 7:30 PM, Dmitry Vyukov wrote:
> On Thu, Mar 31, 2016 at 7:18 PM, Alexander Potapenko
> wrote:
>> On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
>>> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
On Thu, Mar 31, 2016 at 6:00 PM, Mark
On Thu, Mar 31, 2016 at 7:18 PM, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
>> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
>>> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland
On Thu, Mar 31, 2016 at 7:18 PM, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
>> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
>>> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
>>> > On Thu, Mar 31, 2016 at 05:09:29PM +0200,
On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
>> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
>> > On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko
On Thu, Mar 31, 2016 at 7:14 PM, Mark Rutland wrote:
> On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
>> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
>> > On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
>> >> Currently kcov instrumentation is
On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
> > On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
> >> Currently kcov instrumentation is disabled for the following files:
> >
>
On Thu, Mar 31, 2016 at 06:33:24PM +0200, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
> > On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
> >> Currently kcov instrumentation is disabled for the following files:
> >
> >> arch/x86/boot/*
>
On Thu, Mar 31, 2016 at 6:33 PM, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
>> On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
>>> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland
On Thu, Mar 31, 2016 at 6:33 PM, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
>> On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
>>> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
>>> > Hi,
>>> >
>>> > On Thu, Mar 31, 2016 at
On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
> On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
>> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
>> > Hi,
>> >
>> > On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander
On Thu, Mar 31, 2016 at 6:00 PM, Mark Rutland wrote:
> On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
>> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
>> > Hi,
>> >
>> > On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
>> >> Add ARCH_HAS_KCOV to
On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
> > Hi,
> >
> > On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
> >> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
On Thu, Mar 31, 2016 at 05:09:29PM +0200, Alexander Potapenko wrote:
> On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
> > Hi,
> >
> > On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
> >> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
> >>
On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
> Hi,
>
> On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
>> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
>> arch/arm64/lib/delay.c
>
> Why do we disable instrumentation of delay.c?
On Thu, Mar 31, 2016 at 4:29 PM, Mark Rutland wrote:
> Hi,
>
> On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
>> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
>> arch/arm64/lib/delay.c
>
> Why do we disable instrumentation of delay.c?
The main purpose of kcov
Hi,
On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
> arch/arm64/lib/delay.c
Why do we disable instrumentation of delay.c?
What exactly does kcov instrumentation imply? Does it require certain
data to be mapped
Hi,
On Thu, Mar 31, 2016 at 03:54:45PM +0200, Alexander Potapenko wrote:
> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
> arch/arm64/lib/delay.c
Why do we disable instrumentation of delay.c?
What exactly does kcov instrumentation imply? Does it require certain
data to be mapped
On Thu, Mar 31, 2016 at 3:54 PM, Alexander Potapenko wrote:
> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
> arch/arm64/lib/delay.c
>
> Signed-off-by: Alexander Potapenko
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/lib/Makefile | 3
On Thu, Mar 31, 2016 at 3:54 PM, Alexander Potapenko wrote:
> Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
> arch/arm64/lib/delay.c
>
> Signed-off-by: Alexander Potapenko
> ---
> arch/arm64/Kconfig | 1 +
> arch/arm64/lib/Makefile | 3 +++
> 2 files changed, 4
Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
arch/arm64/lib/delay.c
Signed-off-by: Alexander Potapenko
---
arch/arm64/Kconfig | 1 +
arch/arm64/lib/Makefile | 3 +++
2 files changed, 4 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
Add ARCH_HAS_KCOV to ARM64 config. Disable instrumentation of
arch/arm64/lib/delay.c
Signed-off-by: Alexander Potapenko
---
arch/arm64/Kconfig | 1 +
arch/arm64/lib/Makefile | 3 +++
2 files changed, 4 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index
28 matches
Mail list logo