[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFiDJ59KHkh549PBezijr-UektFQtQaZ_5fP5qqRvsVC-e2uxw@mail.gmail.com>
Date: Thu, 24 Apr 2014 14:42:49 +0800
From: Ley Foon Tan <lftan@...era.com>
To: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
Cc: Linux-Arch <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
cltang@...esourcery.com
Subject: Re: [PATCH 08/28] nios2: MMU Fault handling
On Tue, Apr 22, 2014 at 10:30 PM, Ezequiel Garcia
<ezequiel.garcia@...e-electrons.com> wrote:
> Hello Ley Foon,
>
> On Apr 18, Ley Foon Tan wrote:
>> +
>> +bad_area_nosemaphore:
>> + /* User mode accesses just cause a SIGSEGV */
>> + if (user_mode(regs)) {
>
> I found that it's useful to add some printing here, just as ARM
> does. I carry this patch on my kernel:
>
> + printk(KERN_INFO "%s: unhandled page fault (%d) at 0x%08lx, cause %ld\n",
> + current->comm, SIGSEGV, address, cause);
> + show_regs(regs);
>
> Do you think we could do something like it? Maybe with a compile time option?
Yes, this is useful debug message. I can add this.
Prefer not to add new compile time option, I think this shouldn't
happen frequently.
>
>> + _exception(SIGSEGV, regs, code, address);
>> + return;
>> + }
>> +
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists