Re: [patch-RFC 00/26] LTTng Kernel Trace Thread Flag

Mathieu Desnoyers <[email protected]> writes:

> This is an RFC for addition of a new thread flag, TIF_KERNEL_TRACE, to each
> architecture to activate system-wide system call tracing.
> [...]

Instead of creating a new flag, could you overload TIF_SYSCALL_TRACE,
putting the marker into syscall_trace(), and letting !PT_TRACED cause
a skip over the ptrace notification logic?

- FChE
--
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-RFC 00/26] LTTng Kernel Trace Thread Flag
    • From: Mathieu Desnoyers <[email protected]>

• References:
  • [patch-RFC 00/26] LTTng Kernel Trace Thread Flag
    • From: Mathieu Desnoyers <[email protected]>

• Prev by Date: Re: [RFC] [PATCH] A clean approach to writeout throttling
• Next by Date: Re: Allow (O=...) from file
• Previous by thread: [patch-RFC 23/26] Prepare x86_64 for TIF_SYSCALL_TRACE async flag set in entry.S
• Next by thread: Re: [patch-RFC 00/26] LTTng Kernel Trace Thread Flag
• 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]