From: Ingo Molnar <mingo@elte.hu>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: 2.6.29 git master and PAT problems
Date: Wed, 8 Apr 2009 10:17:11 +0200 [thread overview]
Message-ID: <20090408081711.GA4938@elte.hu> (raw)
In-Reply-To: <200904080928.34580.a.miskiewicz@gmail.com>
* Arkadiusz Miskiewicz <a.miskiewicz@gmail.com> wrote:
> On Wednesday 08 of April 2009, Pallipadi, Venkatesh wrote:
> > On Tue, Apr 07, 2009 at 02:12:28AM -0700, Arkadiusz Miskiewicz wrote:
> > > On Tuesday 07 of April 2009, Pallipadi, Venkatesh wrote:
> > > > On Thu, 2009-04-02 at 00:12 -0700, Arkadiusz Miskiewicz wrote:
> > > >
> > > > I was finally able to reproduce the problem of "freeing invalid
> > > > memtype" with upstream git kernel (commit 0221c81b1b) + latest xf86
> > > > intel driver. But, with upstream + the patch I had sent you earlier in
> > > > this thread (http://marc.info/?l=linux-kernel&m=123863345520617&w=2) I
> > > > don't see those freeing invalid memtype errors anymore.
> > > >
> > > > Can you please double check with current git and that patch and let me
> > > > know if you are still seeing the problem.
> > >
> > > Latest linus tree + that patch (it's really applied here), xserver 1.6,
> > > libdrm from git master, intel driver from git master, previously mesa 7.4
> > > (and 7.5 snap currently), tremolous.net 1.1.0 game (tremolous-smp
> > > binary), GM45 gpu.
> > >
> > > To reproduce I just need to run tremolous-smp and connect to some map.
> > > When map finishes loading I instantly get:
> [...]
>
> > OK. One more test patch below, applies over linus's git and you can ignore
> > the earlier patch. The patch below should get rid of the problem and
> > as it removes the track/untrack of vm_insert_pfn completely. This will
> > also eliminate the overhead of hundreds or thousands of entries in
> > pat_memtype_list. Can you please test it.
>
> With this patch I'm no longer able to reproduce problem. Thanks!
Great, thanks!
Venki, mind sending a patch with a proper changelog, Reported-by,
Tested-by tags, with Nick and Andrew Cc:-ed for the memory.c bits,
etc.?
Ingo
next prev parent reply other threads:[~2009-04-08 8:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 21:17 2.6.29 git master and PAT problems Arkadiusz Miskiewicz
2009-03-30 21:22 ` Pallipadi, Venkatesh
2009-03-30 21:31 ` Arkadiusz Miskiewicz
2009-03-30 21:45 ` Pallipadi, Venkatesh
2009-03-30 22:31 ` Arkadiusz Miskiewicz
2009-03-30 23:25 ` Arkadiusz Miskiewicz
2009-03-31 0:21 ` Pallipadi, Venkatesh
2009-03-31 7:44 ` Arkadiusz Miskiewicz
2009-03-31 20:45 ` Yinghai Lu
2009-04-01 12:10 ` Arkadiusz Miskiewicz
2009-03-31 23:21 ` Pallipadi, Venkatesh
2009-04-01 10:23 ` Arkadiusz Miskiewicz
2009-04-01 23:04 ` Pallipadi, Venkatesh
2009-04-02 6:40 ` Arkadiusz Miskiewicz
2009-03-31 0:28 ` Pallipadi, Venkatesh
2009-04-02 0:49 ` Pallipadi, Venkatesh
2009-04-03 9:53 ` Alessandro Suardi
2009-04-03 13:59 ` Pallipadi, Venkatesh
2009-04-06 15:37 ` Alessandro Suardi
2009-04-06 18:40 ` Pallipadi, Venkatesh
[not found] ` <200904020912.23071.a.miskiewicz@gmail.com>
2009-04-06 22:52 ` Pallipadi, Venkatesh
2009-04-07 9:12 ` Arkadiusz Miskiewicz
2009-04-08 1:30 ` Pallipadi, Venkatesh
2009-04-08 7:28 ` Arkadiusz Miskiewicz
2009-04-08 8:17 ` Ingo Molnar [this message]
2009-04-08 22:37 ` Pallipadi, Venkatesh
2009-04-15 17:45 ` Arkadiusz Miskiewicz
2009-04-15 18:12 ` Pallipadi, Venkatesh
2009-04-16 22:47 ` [tip:x86/urgent] x86, PAT: Remove page granularity tracking for vm_insert_pfn maps tip-bot for Pallipadi, Venkatesh
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=20090408081711.GA4938@elte.hu \
--to=mingo@elte.hu \
--cc=a.miskiewicz@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@intel.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