linux-kernel - Re: [PATCH] perf_events: improve x86 event scheduling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bd4cb8901001170642w5d0b79b6jdbb5190a297f45b6@mail.gmail.com>
Date:	Sun, 17 Jan 2010 15:42:16 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, paulus@...ba.org,
	davem@...emloft.net, perfmon2-devel@...ts.sf.net
Subject: Re: [PATCH] perf_events: improve x86 event scheduling

Frederic,


Here is what I have now in the x86 code.

As for your comment on disabling the x86 event, we don't
need to do this because it is not actually activated yet when
we return from hw_perf_group_sched_in(). Activation occurs
really in hw_perf_enable().


static int x86_event_sched_in(struct perf_event *event,
                          struct perf_cpu_context *cpuctx, int cpu)
{
        int ret = 0;

        event->state = PERF_EVENT_STATE_ACTIVE;
        event->oncpu = cpu;
        event->tstamp_running += event->ctx->time - event->tstamp_stopped;

        if (is_software_event(event))
                ret = event->pmu->enable(event);

        if (!ret && !is_software_event(event))
                cpuctx->active_oncpu++;

        if (!ret && event->attr.exclusive)
                cpuctx->exclusive = 1;

        return ret;
}

static void x86_event_sched_out(struct perf_event *event,
                            struct perf_cpu_context *cpuctx, int cpu)
{
        event->state = PERF_EVENT_STATE_INACTIVE;
        event->oncpu = -1;

        event->tstamp_running -= event->ctx->time - event->tstamp_stopped;

        if (is_software_event(event))
                event->pmu->disable(event);

        if (!is_software_event(event))
                cpuctx->active_oncpu--;

        if (event->attr.exclusive || !cpuctx->active_oncpu)
                cpuctx->exclusive = 0;
}


On Sun, Jan 17, 2010 at 3:12 PM, Frederic Weisbecker <fweisbec@...il.com> wrote:
> On Wed, Jan 13, 2010 at 06:22:54PM +0100, Stephane Eranian wrote:
>> Ok,
>>
>> Something like that should problably do it:
>>
>> static void event_sched_out(struct perf_event *event, int cpu)
>> {
>>         event->state = PERF_EVENT_STATE_INACTIVE;
>>         event->oncpu = -1;
>> }
>
>
>
> You need to also call pmu->disable() if it is a software event,
> because a breakpoint needs to be unregistered in hardware level
> too.
>
> And disable it in x86 level if it is an x86 event?
>
>
>
>> hw_perf_group_sched_in()
>> {
>>        ....
>>        n = 1;
>>         list_for_each_entry(sub, &leader->sibling_list, group_entry) {
>>                 if (sub->state > PERF_EVENT_STATE_OFF) {
>>                         ret = event_sched_in(sub, cpu);
>>                         if (ret)
>>                                 goto undo;
>
>
>
> Yeah we indeed really need to check that.
>
> Thanks.
>
>



-- 
Stephane Eranian  | EMEA Software Engineering
Google France | 38 avenue de l'Opéra | 75002 Paris
Tel : +33 (0) 1 42 68 53 00
This email may be confidential or privileged. If you received this
communication by mistake, please
don't forward it to anyone else, please erase all copies and
attachments, and please let me know that
it went to the wrong person. Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/