From: Jiri Olsa <jolsa@redhat.com>
To: mingo@elte.hu, rostedt@goodmis.org, yhlu.kernel@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: [RFC 0/2] apic: tracing IPI events
Date: Thu, 5 Aug 2010 13:09:36 +0200 [thread overview]
Message-ID: <1281006578-5073-1-git-send-email-jolsa@redhat.com> (raw)
hi,
I'm adding tracing of IPIs to the APIC code by hooking
following apic callbacks:
void (*send_IPI_mask)(const struct cpumask *mask, int vector);
void (*send_IPI_mask_allbutself)(const struct cpumask *mask,
int vector);
void (*send_IPI_allbutself)(int vector);
void (*send_IPI_all)(int vector);
void (*send_IPI_self)(int vector);
attached patches:
- 1/2 apic: adding apic_send_IPI_* methods for apic's IPI callbacks
- 2/2 apic,trace: IPI sent trace event.
I'm not sure this is the best way, maybe some more
general approach might be better.
please let me know what you think
wbr,
jirka
---
arch/x86/include/asm/apic.h | 16 +++++++++-
arch/x86/include/asm/apic_trace.h | 53 +++++++++++++++++++++++++++++++
arch/x86/include/asm/ipi.h | 4 +-
arch/x86/kernel/apic/apic.c | 48 +++++++++++++++++++++++++++-
arch/x86/kernel/apic/apic_flat_64.c | 4 +-
arch/x86/kernel/apic/hw_nmi.c | 2 +-
arch/x86/kernel/apic/io_apic.c | 9 +++--
arch/x86/kernel/apic/nmi.c | 2 +-
arch/x86/kernel/apic/probe_64.c | 2 +-
arch/x86/kernel/cpu/mcheck/mce-inject.c | 2 +-
arch/x86/kernel/cpu/mcheck/mce.c | 2 +-
arch/x86/kernel/cpu/perf_event.c | 2 +-
arch/x86/kernel/kgdb.c | 2 +-
arch/x86/kernel/reboot.c | 2 +-
arch/x86/kernel/smp.c | 12 +++---
arch/x86/mm/tlb.c | 2 +-
16 files changed, 139 insertions(+), 25 deletions(-)
next reply other threads:[~2010-08-05 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:09 Jiri Olsa [this message]
2010-08-05 11:09 ` [PATCH 1/2] apic: adding apic_send_IPI_* methods for apic's IPI callbacks Jiri Olsa
2010-08-05 11:09 ` [PATCH 2/2] apic,trace: IPI sent trace event Jiri Olsa
2010-08-06 11:26 ` [RFC 0/2] apic: tracing IPI events Andi Kleen
2010-08-06 11:46 ` Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1281006578-5073-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®