From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ben Tebulin <tebulin@googlemail.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Balbir Singh <bsingharora@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [Bug] Reproducible data corruption on i5-3340M: Please continue your great work! :-)
Date: Fri, 16 Aug 2013 13:28:32 +0200 [thread overview]
Message-ID: <20130816112832.GY24092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20130816110031.GA13507@dhcp22.suse.cz>
On Fri, Aug 16, 2013 at 01:00:31PM +0200, Michal Hocko wrote:
> I was thinking about teaching __tlb_remove_page to update the range
> automatically from the given address.
The mmu_gather unification stuff I had did it differently still:
http://permalink.gmane.org/gmane.linux.kernel.mm/81287
That said, I do like Linus' approach. The only thing I haven't
considered is if it does the right thing for tile,mips-r4k which have
'special' rules for VM_HUGETLB. Although I don't think it changes those
archs enough to break anything.
I should find some time to finally finish that series :/
--
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: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ben Tebulin <tebulin@googlemail.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Balbir Singh <bsingharora@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [Bug] Reproducible data corruption on i5-3340M: Please continue your great work! :-)
Date: Fri, 16 Aug 2013 13:28:32 +0200 [thread overview]
Message-ID: <20130816112832.GY24092@twins.programming.kicks-ass.net> (raw)
Message-ID: <20130816112832.KPr9bv4iLmcuIv8qw0Lda3ss-19j2AGPjg6Z3qwRsOA@z> (raw)
In-Reply-To: <20130816110031.GA13507@dhcp22.suse.cz>
On Fri, Aug 16, 2013 at 01:00:31PM +0200, Michal Hocko wrote:
> I was thinking about teaching __tlb_remove_page to update the range
> automatically from the given address.
The mmu_gather unification stuff I had did it differently still:
http://permalink.gmane.org/gmane.linux.kernel.mm/81287
That said, I do like Linus' approach. The only thing I haven't
considered is if it does the right thing for tile,mips-r4k which have
'special' rules for VM_HUGETLB. Although I don't think it changes those
archs enough to break anything.
I should find some time to finally finish that series :/
next prev parent reply other threads:[~2013-08-16 11:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 14:58 Reproducible git-fsck/SHA1 failures since 3.7.x on a Dell E6430 / i5-3340M Ben Tebulin
2013-08-12 8:04 ` Reproducible data corruption since 3.7.x on i5-3340M machines Ben Tebulin
2013-08-14 16:36 ` [Bug] Reproducible data corruption on i5-3340M: Please revert 53a59fc67! Ben Tebulin
2013-08-14 17:40 ` Michal Hocko
2013-08-14 17:40 ` Michal Hocko
2013-08-14 17:58 ` Michal Hocko
2013-08-14 17:58 ` Michal Hocko
2013-08-14 18:03 ` Linus Torvalds
2013-08-14 18:03 ` Linus Torvalds
2013-08-14 18:28 ` Michal Hocko
2013-08-14 18:28 ` Michal Hocko
2013-08-14 18:35 ` Linus Torvalds
2013-08-14 18:35 ` Linus Torvalds
2013-08-15 9:25 ` Ben Tebulin
2013-08-15 9:25 ` Ben Tebulin
2013-08-15 12:02 ` Linus Torvalds
2013-08-15 12:02 ` Linus Torvalds
2013-08-15 12:37 ` Ben Tebulin
2013-08-15 12:37 ` Ben Tebulin
2013-08-15 13:40 ` Michal Hocko
2013-08-15 13:40 ` Michal Hocko
2013-08-15 14:46 ` Michal Hocko
2013-08-15 14:46 ` Michal Hocko
2013-08-15 14:53 ` Michal Hocko
2013-08-15 14:53 ` Michal Hocko
2013-08-15 15:14 ` Michal Hocko
2013-08-15 15:14 ` Michal Hocko
2013-08-15 18:00 ` Linus Torvalds
2013-08-15 18:29 ` Bjørn Mork
2013-08-15 18:29 ` Bjørn Mork
2013-08-15 18:29 ` Bjørn Mork
2013-08-15 18:42 ` Linus Torvalds
2013-08-15 18:42 ` Linus Torvalds
2013-08-15 23:05 ` [Bug] Reproducible data corruption on i5-3340M: Please continue your great work! :-) Ben Tebulin
2013-08-15 23:05 ` Ben Tebulin
2013-08-16 0:33 ` Linus Torvalds
2013-08-16 6:22 ` Stephen Rothwell
2013-08-16 7:55 ` richard -rw- weinberger
2013-08-16 7:55 ` richard -rw- weinberger
2013-08-16 11:00 ` Michal Hocko
2013-08-16 11:00 ` Michal Hocko
2013-08-16 11:28 ` Peter Zijlstra [this message]
2013-08-16 11:28 ` Peter Zijlstra
2013-08-16 23:40 ` Tony Luck
2013-08-16 23:40 ` Tony Luck
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=20130816112832.GY24092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=riel@redhat.com \
--cc=tebulin@googlemail.com \
--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.