public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-540-gcb1fb1e Date: Thu, 01 Dec 2011 19:43:00 -0000 [thread overview] Message-ID: <20111201194346.32112.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via cb1fb1e7aec8f68a13301d046c19e9f7886f347b (commit) from 2ffd883f5ad3d4fe3763a267a3a446e3b5f1285c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit cb1fb1e7aec8f68a13301d046c19e9f7886f347b Author: Mark Wielaard <mjw@redhat.com> Date: Thu Dec 1 20:26:19 2011 +0100 _stp_get_mm_counter: Fix kernel version check. The kernel version check was wrong in two ways. First it tested against kernel_v >= "3.1.0" but linux commit 172703 "mm: delete non-atomic mm counter implementation" was actually integrated for 3.0. But fedora names their 3.0 kernels 2.6.40 (and 3.1 kernels 2.6.41, depending on release). So change the test to kernel_v >= "2.6.40". The reason this wasn't found earlier was that there is another check for CONFIG_NR_CPUS >= CONFIG_SPLIT_PTLOCK_CPUS which is almost always true (but not on arm tegra kernels). ----------------------------------------------------------------------- Summary of changes: tapset/proc_mem.stp | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-01 19:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111201194346.32112.qmail@sourceware.org \ --to=mark@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).