From: Byungchul Park <byungchul.park@lge.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: peterz@infradead.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@lge.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default
Date: Thu, 19 Oct 2017 15:36:11 +0900 [thread overview]
Message-ID: <20171019063610.GD3310@X58A-UD3R> (raw)
In-Reply-To: <20171019062212.n55vzg4khtds3mqk@gmail.com>
On Thu, Oct 19, 2017 at 08:22:12AM +0200, Ingo Molnar wrote:
> There's no current crash regression that I know of - I'm just outlining the
> conditions of getting all this re-enabled in the next merge window.
>
> Instead of sending two series, could you please send a series that includes both
> these fixing + re-enabling patches, plus the false positive fixes?
>
> In particular I think the cross-release re-enabling should be done as the last
> patch, so that any future bisections of new false positives won't be made more
> difficult by re-introducing the old false positives near the end of the bisection.
I agree. But I already sent v2 before you told me..
Do you want me to send patches fixing false positives in the thread
fixing performance regression?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Byungchul Park <byungchul.park@lge.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: peterz@infradead.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@lge.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default
Date: Thu, 19 Oct 2017 15:36:11 +0900 [thread overview]
Message-ID: <20171019063610.GD3310@X58A-UD3R> (raw)
In-Reply-To: <20171019062212.n55vzg4khtds3mqk@gmail.com>
On Thu, Oct 19, 2017 at 08:22:12AM +0200, Ingo Molnar wrote:
> There's no current crash regression that I know of - I'm just outlining the
> conditions of getting all this re-enabled in the next merge window.
>
> Instead of sending two series, could you please send a series that includes both
> these fixing + re-enabling patches, plus the false positive fixes?
>
> In particular I think the cross-release re-enabling should be done as the last
> patch, so that any future bisections of new false positives won't be made more
> difficult by re-introducing the old false positives near the end of the bisection.
I agree. But I already sent v2 before you told me..
Do you want me to send patches fixing false positives in the thread
fixing performance regression?
next prev parent reply other threads:[~2017-10-19 6:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 9:13 [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default Byungchul Park
2017-10-18 9:13 ` Byungchul Park
2017-10-18 9:13 ` [PATCH 2/2] lockdep: Remove BROKEN flag of LOCKDEP_CROSSRELEASE Byungchul Park
2017-10-18 9:13 ` Byungchul Park
2017-10-18 10:12 ` Ingo Molnar
2017-10-18 10:12 ` Ingo Molnar
2017-10-19 1:58 ` Byungchul Park
2017-10-19 1:58 ` Byungchul Park
2017-10-18 10:09 ` [PATCH 1/2] lockdep: Introduce CROSSRELEASE_STACK_TRACE and make it not unwind as default Ingo Molnar
2017-10-18 10:09 ` Ingo Molnar
2017-10-19 4:32 ` Byungchul Park
2017-10-19 4:32 ` Byungchul Park
2017-10-19 5:57 ` Ingo Molnar
2017-10-19 5:57 ` Ingo Molnar
2017-10-19 6:11 ` Byungchul Park
2017-10-19 6:11 ` Byungchul Park
2017-10-19 6:22 ` Ingo Molnar
2017-10-19 6:22 ` Ingo Molnar
2017-10-19 6:36 ` Byungchul Park [this message]
2017-10-19 6:36 ` Byungchul Park
2017-10-19 8:05 ` Ingo Molnar
2017-10-19 8:05 ` Ingo Molnar
2017-10-19 6:22 ` Byungchul Park
2017-10-19 6:22 ` Byungchul Park
2017-10-19 8:10 ` Ingo Molnar
2017-10-19 8:10 ` Ingo Molnar
2017-10-19 9:02 ` 박병철/선임연구원/SW Platform(연)AOT팀(byungchul.park@lge.com)
2017-10-19 9:02 ` 박병철/선임연구원/SW Platform(연)AOT팀(byungchul.park@lge.com)
2017-10-19 9:41 ` Ingo Molnar
2017-10-19 9:41 ` Ingo Molnar
2017-10-18 13:23 ` Thomas Gleixner
2017-10-18 13:23 ` Thomas Gleixner
2017-10-18 13:30 ` Ingo Molnar
2017-10-18 13:30 ` Ingo Molnar
2017-10-18 13:36 ` Thomas Gleixner
2017-10-18 13:36 ` Thomas Gleixner
2017-10-18 14:15 ` Matthew Wilcox
2017-10-18 14:15 ` Matthew Wilcox
2017-10-18 14:35 ` Thomas Gleixner
2017-10-18 14:35 ` Thomas Gleixner
2017-10-18 17:05 ` Ingo Molnar
2017-10-18 17:05 ` Ingo Molnar
2017-10-19 2:00 ` Byungchul Park
2017-10-19 2:00 ` Byungchul Park
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=20171019063610.GD3310@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.