Hi,
I forgot about the set of issues below. Michael had a suggested powerpc
fix for 3, but it it would be nice to fix the perf bugs in 1 and 2.
Anton
--
> Updating to mainline as of last night, I started seeing the following
> error when running the perf report TUI:
>
> 0x46068 [0x8]: failed to
Anton Blanchard writes:
>> > 14c00-14c00 g exc_virt_0x4c00_system_call
>>^
>>What's this? The address? If so it's wrong?
>
> Offset into the binary I think, there's one 64kB page of ELF gunk at
> the start.
Ah OK makes sense.
>> So more digging required.
>
> Thanks for checking, it's
Hi Michael,
> > 14c00-14c00 g exc_virt_0x4c00_system_call
>^
>What's this? The address? If so it's wrong?
Offset into the binary I think, there's one 64kB page of ELF gunk at
the start.
> Seems likely. But I can't see why.
>
> AFAICS we have never emitted a size for those symbols:
>
On Mon, 10 Oct 2016 16:02:07 +1100
Michael Ellerman wrote:
> Anton Blanchard writes:
>
> > Hi,
> >
> > Updating to mainline as of last night, I started seeing the following
> > error when running the perf report TUI:
> >
> > 0x46068 [0x8]: failed to process type: 68
> >
> > This event is just P
Anton Blanchard writes:
> Hi,
>
> Updating to mainline as of last night, I started seeing the following
> error when running the perf report TUI:
>
> 0x46068 [0x8]: failed to process type: 68
>
> This event is just PERF_RECORD_FINISHED_ROUND:
>
> 0x46068 [0x8]: event: 68
> .
> . ... raw event: si
Hi,
Updating to mainline as of last night, I started seeing the following
error when running the perf report TUI:
0x46068 [0x8]: failed to process type: 68
This event is just PERF_RECORD_FINISHED_ROUND:
0x46068 [0x8]: event: 68
.
. ... raw event: size 8 bytes
. : 44 00 00 00 00 00 08 00
6 matches
Mail list logo
