Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

On Thu, May 13, 2010 at 2:39 PM, Felipe Contreras wrote: > On Thu, May 13, 2010 at 12:09 AM, Guzman Lugo, Fernando > wrote: >>> If you are referring to this patch: >>> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap- >>> 2.6.git;a=commit;h=26ad62f03578a12e942d8bb86d0e52ef1afdee22 >> >

Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

On Fri, May 14, 2010 at 12:15 AM, Guzman Lugo, Fernando wrote: >> But the DSP is not dumping the stack there, from what I can see >> bridge_brd_read() is used to read DSP internal memory. > > DSP is dumping the stack after the MMUFault and mmu let DSP to continue. > > Let's see what happens in suc

RE: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

r; Menon, Nishanth > Subject: Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after > DSP_MMUFAULT > > On Thu, May 13, 2010 at 8:29 PM, Guzman Lugo, Fernando > wrote: > >> First of all, what is the DSP supposed to do with that memory? Do we > >> really n

Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

On Thu, May 13, 2010 at 8:29 PM, Guzman Lugo, Fernando wrote: >> First of all, what is the DSP supposed to do with that memory? Do we >> really need to call hw_mmu_tlb_add at all? > > Once DSP MMUfault happens iva mmu module prevents DSP continue executing > until mmu module is able get some phys

RE: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

r; Menon, Nishanth > Subject: Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after > DSP_MMUFAULT > > On Thu, May 13, 2010 at 12:09 AM, Guzman Lugo, Fernando > wrote: > >> If you are referring to this patch: > >> http://git.kernel.org/?p=linux/ke

Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

On Thu, May 13, 2010 at 12:09 AM, Guzman Lugo, Fernando wrote: >> If you are referring to this patch: >> http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap- >> 2.6.git;a=commit;h=26ad62f03578a12e942d8bb86d0e52ef1afdee22 > > Yes, that's the patch. Could you make sure that the GPT8 interrup

RE: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

r; Menon, Nishanth > Subject: Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after > DSP_MMUFAULT > > Hi, > > I didn't touch this issue in the hopes that it would be fixed, but > seems it hasn't. > > On Mon, Apr 19, 2010 at 9:25 PM, Guzman Lugo, Fer

Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

Hi, I didn't touch this issue in the hopes that it would be fixed, but seems it hasn't. On Mon, Apr 19, 2010 at 9:25 PM, Guzman Lugo, Fernando wrote: > To sum up: > > - "DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT" is only > hidden the problem, we don't need aligned memory

RE: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

Hi all, I have found the really issue here: The problem here is that after MMUFault the DSP is allowed to continue executing until here revices the message informing about the MMUFault and this problem since the patches for mailbox migration. Previous code:

Re: [PATCH] DSPBRIDGE:Fix Kernel memory poison overwritten after DSP_MMUFAULT

Please ignore this patch. Thanks, Deepak Chitriki Rudramuni, Deepak wrote: kmalloc() does not guarantee page aligned memory always,hence resulting in virtual addresses not getting aligned to page boundary. This patch replaces kmalloc() with __get_free_pages() which allocates kernel memory in te