From: Larry Finger <Larry.Finger@lwfinger.net>
To: Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@kernel.org>,
Matthew Wilcox <willy@infradead.org>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: Sleeping BUG in khugepaged for i586
Date: Fri, 9 Jun 2017 09:28:33 -0500 [thread overview]
Message-ID: <20924f94-1959-338c-b585-0c69a895aa39@lwfinger.net> (raw)
In-Reply-To: <d348054d-3857-65bb-e896-c4bd2ea6ee85@suse.cz>
On 06/09/2017 01:48 AM, Vlastimil Babka wrote:
> On 06/08/2017 10:30 PM, Michal Hocko wrote:
>> But I guess you are primary after syncing the preemptive mode for 64 and
>> 32b systems, right? I agree that having a different model is more than
>> unfortunate because 32b gets much less testing coverage and so a risk of
>> introducing a new bug is just a matter of time. Maybe we should make
>> pte_offset_map disable preemption and currently noop pte_unmap to
>> preempt_enable. The overhead should be pretty marginal on x86_64 but not
>> all arches have per-cpu preempt count. So I am not sure we really want
>> to add this to just for the debugging purposes...
>
> I think adding that overhead for everyone would be unfortunate. It would
> be acceptable, if it was done only for the config option that enables
> the might_sleep() checks (CONFIG_DEBUG_ATOMIC_SLEEP?)
As a "heads up", I will not be available for any testing from June 10 through
June 17.
Larry
--
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>
next prev parent reply other threads:[~2017-06-09 14:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 19:24 Larry Finger
2017-06-05 21:44 ` Andrew Morton
2017-06-06 14:02 ` Vlastimil Babka
2017-06-06 15:01 ` Larry Finger
2017-06-07 7:19 ` Vlastimil Babka
2017-06-07 20:56 ` David Rientjes
2017-06-08 14:48 ` Michal Hocko
2017-06-08 17:05 ` Matthew Wilcox
2017-06-08 20:18 ` Michal Hocko
2017-06-08 20:30 ` Michal Hocko
2017-06-09 6:48 ` Vlastimil Babka
2017-06-09 7:43 ` Michal Hocko
2017-06-09 14:28 ` Larry Finger [this message]
2017-06-09 22:38 ` David Rientjes
2017-06-10 8:09 ` Michal Hocko
2017-06-11 23:28 ` David Rientjes
2017-06-12 6:29 ` Michal Hocko
2017-06-15 0:28 ` David Rientjes
2017-06-15 1:12 ` David Rientjes
2017-06-15 8:32 ` Michal Hocko
2017-06-23 12:08 ` Michal Hocko
2017-06-23 13:13 ` Vlastimil Babka
2017-06-23 13:25 ` Michal Hocko
2017-06-23 15:28 ` Larry Finger
2017-06-08 15:29 ` Larry Finger
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=20924f94-1959-338c-b585-0c69a895aa39@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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