From: Ingo Molnar <mingo@kernel.org>
To: Alex Snast <asnast@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 1/2] perf tools: Use postorder rbtree iteration when removing symbols
Date: Mon, 21 Sep 2015 09:17:54 +0200 [thread overview]
Message-ID: <20150921071754.GB27624@gmail.com> (raw)
In-Reply-To: <CAMqsXBcZAS6hCh8LdHjFGiji8dwHLQus1xf5OnK7CZEjrbx33w@mail.gmail.com>
* Alex Snast <asnast@gmail.com> wrote:
> What's the benefit of having that diverge check script as on every commit you'll
> either add the new stuff to tools/include/linux/rbtree.h or add an exception to
> that script as in rb_link_node_rcu case.
The benefit is that things do not diverge - diff or md5sum is fast enough.
I don't think exceptions should be added, we should find ways to make the files
100% identical.
> And are you suggesting to check for divergence for everything under tools/
> include/linux recursively?
No, on a case by case basis, for bigger 'facility files' we copied from the kernel
source.
rbtree.h and rbtree.c certainly applies: for example we've got interval rbtree
additions in -tip that would be nice to merge upstream:
tools/kvm/include/kvm/rbtree-interval.h
tools/kvm/util/rbtree-interval.c
... but which have bitrotten meanwhile, making the copy out of sync and harder to
merge. Making sure the files are properly upstreamed during build time makes sure
things don't get out of sync.
Thanks,
Ingo
prev parent reply other threads:[~2015-09-21 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 13:03 [PATCH 1/2] perf tools: Use postorder rbtree iteration when removing symbols Alex Snast
2015-09-19 13:03 ` [PATCH 2/2] perf tools: Use rb_entry_safe on first / next symbol lookup Alex Snast
2015-09-20 8:05 ` [PATCH 1/2] perf tools: Use postorder rbtree iteration when removing symbols Ingo Molnar
[not found] ` <CAMqsXBcZAS6hCh8LdHjFGiji8dwHLQus1xf5OnK7CZEjrbx33w@mail.gmail.com>
2015-09-21 7:17 ` Ingo Molnar [this message]
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=20150921071754.GB27624@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=asnast@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.