On Fri, May 7, 2010 at 1:38 PM, Paul Mackerras wrote:
> On Thu, May 06, 2010 at 12:28:44PM +0800, Li Yang wrote:
>
>> The root cause of this oops might not be related with the vmalloc'ed
>> area processing in Instruction Storage Interrupt. But x86 does have
>> the code for processing it while we
On Thu, May 06, 2010 at 12:28:44PM +0800, Li Yang wrote:
> The root cause of this oops might not be related with the vmalloc'ed
> area processing in Instruction Storage Interrupt. But x86 does have
> the code for processing it while we don't. Is it because we have
> nothing to do with the vmallo
On Wed, May 5, 2010 at 7:51 PM, Timur Tabi wrote:
> On Wed, May 5, 2010 at 12:19 AM, Li Yang-R58472 wrote:
>> I got a weird page fault oops on vmalloc'ed area. Digging into the powerpc
>> do_page_fault(), I found there is no handling of address in kernel space
>> unlike the x86 counter part.
On Wed, May 5, 2010 at 12:19 AM, Li Yang-R58472 wrote:
> I got a weird page fault oops on vmalloc'ed area. Digging into the powerpc
> do_page_fault(), I found there is no handling of address in kernel space
> unlike the x86 counter part. Does any one know how we deal with the
> vmalloc'ed are
Hi all,
I got a weird page fault oops on vmalloc'ed area. Digging into the powerpc
do_page_fault(), I found there is no handling of address in kernel space unlike
the x86 counter part. Does any one know how we deal with the vmalloc'ed area
on powerpc? Thanks a lot.
- Leo
___
