Re: [patch 9/9] Scheduler profiling - Use conditional calls

Mathieu Desnoyers <[email protected]> writes:
>  	}
> -	profile_hit(SCHED_PROFILING, __builtin_return_address(0));
> +	cond_call(profile_on,
> +		profile_hit(SCHED_PROFILING, __builtin_return_address(0)));

Would it be possible to use a syntax like

        if (unlikely_cond_call(variable)) {     (or better name) 
                ...
        } 

instead? I think that would be much nicer to read than having
code in a macro argument

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 9/9] Scheduler profiling - Use conditional calls
    • From: Mathieu Desnoyers <[email protected]>

• References:
  • [patch 0/9] Conditional Calls - for 2.6.22-rc2-mm1
    • From: Mathieu Desnoyers <[email protected]>
  • [patch 9/9] Scheduler profiling - Use conditional calls
    • From: Mathieu Desnoyers <[email protected]>

• Prev by Date: RE: kexec and aacraid broken
• Next by Date: Re: [patch 2/9] Conditional Calls - Hash Table
• Previous by thread: Re: [patch 9/9] Scheduler profiling - Use conditional calls
• Next by thread: Re: [patch 9/9] Scheduler profiling - Use conditional calls
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]