From: Steven Rostedt <srostedt@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the kmemcheck tree with the tracing tree
Date: Mon, 01 Jun 2009 10:33:19 -0400 [thread overview]
Message-ID: <1243866799.18138.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20090601175539.67317265.sfr@canb.auug.org.au>
On Mon, 2009-06-01 at 17:55 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kmemcheck tree got a conflict in
> kernel/trace/ring_buffer.c between commit
> aa20ae8444fc6c318272c643f856d8d8ad3e198d ("ring-buffer: move big if
> statement down") from the tracing tree and commits
> 9b7ff384ee76ced9638ab236db588a6f13916336 ("trace: annotate bitfields in
> struct ring_buffer_event") and 3467e18b1cf34c7d316af5717e7053ce845d014e
> ("kmemcheck: make bitfield annotations be valid C") from the kmemcheck
> tree.
>
> I fixed it up (see below) and can carry the fix as necessary.
I'm not great at reading git conflict diffs.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc kernel/trace/ring_buffer.c
> index 3611706,c22506f..0000000
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@@ -1154,156 -1156,132 +1155,157 @@@ static unsigned rb_calculate_event_leng
> return length;
> }
[...]
> + /*
> + * The actual tail page has moved forward.
> + */
> + if (tail < BUF_PAGE_SIZE) {
> + /* Mark the rest of the page with padding */
> + event = __rb_page_index(tail_page, tail);
> ++ kmemcheck_annotate_bitfield(event, bitfield);
Is this...
> + rb_event_set_padding(event);
> + }
>
> - /*
> - * The actual tail page has moved forward.
> - */
> - if (tail < BUF_PAGE_SIZE) {
> - /* Mark the rest of the page with padding */
> - event = __rb_page_index(tail_page, tail);
> - kmemcheck_annotate_bitfield(event, bitfield);
> - rb_event_set_padding(event);
> - }
[...]
>
> @@@ -1311,12 -1289,9 +1313,13 @@@
> return NULL;
>
> event = __rb_page_index(tail_page, tail);
> + kmemcheck_annotate_bitfield(event, bitfield);
and this the only changes you needed to fix?
-- Steve
> rb_update_event(event, type, length);
>
> + /* The passed in type is zero for DATA */
> + if (likely(!type))
> + local_inc(&tail_page->entries);
> +
> /*
> * If this is a commit and the tail is zero, then update
> * this page's time stamp.
next prev parent reply other threads:[~2009-06-01 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 7:55 linux-next: manual merge of the kmemcheck tree with the tracing tree Stephen Rothwell
2009-06-01 14:33 ` Steven Rostedt [this message]
2009-06-02 0:32 ` Stephen Rothwell
2009-06-01 19:46 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-06-01 7:55 Stephen Rothwell
2009-03-06 6:27 Stephen Rothwell
2009-03-06 8:14 ` Vegard Nossum
2009-03-06 10:27 ` Ingo Molnar
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=1243866799.18138.9.camel@localhost.localdomain \
--to=srostedt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.au \
--cc=vegard.nossum@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