From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 0/8] stm class/intel_th: Updates for v5.10
Date: Mon, 5 Oct 2020 10:13:11 +0300 [thread overview]
Message-ID: <20201005071319.78508-1-alexander.shishkin@linux.intel.com> (raw)
Hi Greg,
Apologies for the late posting. These are the updates that I have for
the next merge window if that's still doable.
Six patches add support for exporting more of ftrace via STM, 3 of them
get into ftrace territory, but Steven reviewed all of them and there
should be no conflicts.
Two patches add new PCI IDs to the Intel TH driver, which would normally
go in a "fixes" patchset, but this late in the cycle that doesn't make
much sense, so they are included in the same series.
Alexander Shishkin (2):
intel_th: pci: Add Alder Lake-S support
intel_th: pci: Add Alder Lake CPU support
Tingwei Zhang (6):
stm class: ftrace: Change dependency to TRACING
tracing: Add flag to control different traces
tracing: Add trace_export support for event trace
tracing: Add trace_export support for trace_marker
stm class: ftrace: Enable supported trace export flag
stm class: ftrace: Use different channel accroding to CPU
drivers/hwtracing/intel_th/pci.c | 10 ++
drivers/hwtracing/stm/Kconfig | 2 +-
drivers/hwtracing/stm/ftrace.c | 7 +-
include/linux/trace.h | 7 +
kernel/trace/trace.c | 270 +++++++++++++++++--------------
5 files changed, 169 insertions(+), 127 deletions(-)
--
2.28.0
next reply other threads:[~2020-10-05 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:13 Alexander Shishkin [this message]
2020-10-05 7:13 ` [PATCH 1/8] stm class: ftrace: Change dependency to TRACING Alexander Shishkin
2020-10-05 7:13 ` [PATCH 2/8] tracing: Add flag to control different traces Alexander Shishkin
2020-10-05 7:13 ` [PATCH 3/8] tracing: Add trace_export support for event trace Alexander Shishkin
2020-10-05 7:13 ` [PATCH 4/8] tracing: Add trace_export support for trace_marker Alexander Shishkin
2020-10-05 7:13 ` [PATCH 5/8] stm class: ftrace: Enable supported trace export flag Alexander Shishkin
2020-10-05 7:13 ` [PATCH 6/8] stm class: ftrace: Use different channel accroding to CPU Alexander Shishkin
2020-10-05 7:13 ` [PATCH 7/8] intel_th: pci: Add Alder Lake-S support Alexander Shishkin
2020-10-05 7:13 ` [PATCH 8/8] intel_th: pci: Add Alder Lake CPU support Alexander Shishkin
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=20201005071319.78508-1-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome