From: ak
Using autofdo is currently something difficult. It requires using the
model specific branches taken event, which differs on different CPUs.
The example shown in the manual requires a special patched version of
perf that is non standard, and also will likely not work everywhere.
This pat
On Wed, Jun 22, 2016 at 11:34:05PM +0200, Bernhard Reutner-Fischer wrote:
> >+for m in mod[:-1]:
> >+print "model*:\ %s|\\" % m
> >+print 'model*:\ %s) E="%s$FLAGS" ;;' % (mod[-1], event)
> >+print '''*)
> >+echo >&2 "Unknown CPU. Run contrib/gen_autofdo_event.py --a
On June 22, 2016 2:37:04 PM GMT+02:00, Andi Kleen wrote:
>From: Andi Kleen
>
>Using autofdo is currently something difficult. It requires using the
>model specific branches taken event, which differs on different CPUs.
>The example shown in the manual requires a special patched version of
>perf t
On 06/22/2016 11:44 AM, Andi Kleen wrote:
2016-06-22 Andi Kleen
* config/i386/gcc-auto-profile: New file.
contrib/:
2016-06-22 Andi Kleen
* gen_autofdo_event.py: New file to regenerate
gcc-auto-profile.
This part looks fine to me and can probably go in independe
> > 2016-06-22 Andi Kleen
> >
> > * config/i386/gcc-auto-profile: New file.
> >
> > contrib/:
> >
> > 2016-06-22 Andi Kleen
> >
> > * gen_autofdo_event.py: New file to regenerate
> > gcc-auto-profile.
> This part looks fine to me and can probably go in independently of the oth
On 06/22/2016 06:37 AM, Andi Kleen wrote:
From: Andi Kleen
Using autofdo is currently something difficult. It requires using the
model specific branches taken event, which differs on different CPUs.
The example shown in the manual requires a special patched version of
perf that is non standard,
From: Andi Kleen
Using autofdo is currently something difficult. It requires using the
model specific branches taken event, which differs on different CPUs.
The example shown in the manual requires a special patched version of
perf that is non standard, and also will likely not work everywhere.
