From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: "Matthew Fredrickson" <creslin@digium.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Device Driver Etiquette
Date: Sun, 3 Jun 2007 07:15:39 +0530 [thread overview]
Message-ID: <a781481a0706021845y2fd8442fy388c0df58aabcedc@mail.gmail.com> (raw)
In-Reply-To: <1180826520.2815.3.camel@laptopd505.fenrus.org>
On 6/3/07, Arjan van de Ven <arjan@infradead.org> wrote:
> On Fri, 2007-06-01 at 12:47 -0500, Matthew Fredrickson wrote:
>
> > My question is this: is there a way to either work around the problem I
> > am seeing with the stack without recompiling the kernel with 8K stack
> > size or without disabling irqs for such a long period of time (which I
> > think is not a nice thing to do either) OR is it acceptable (although
> > not nice) to simply fix it this way, by disabling irqs while it loads
> > the firmware?
>
> I wonder if you're chasing ghosts; 4K stack kernels have a seperate
> stack for interrupts so... those should be safe.
Argh, yes, thanks for reminding/correcting all of us :-)
> Btw, you forgot to post a pointer to the source code of your driver, so
> it's a lot harder for us (read: impossible) to give you good advice..
Right, and dmesg / debug output of when things go wrong is also
needed at the very least to confirm whether or not there is really a
stack overflow issue here in the first place.
Satyam
next prev parent reply other threads:[~2007-06-03 1:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 17:47 Matthew Fredrickson
2007-06-01 18:38 ` Lee Revell
2007-06-01 22:28 ` H. Peter Anvin
2007-06-02 15:05 ` Satyam Sharma
2007-06-02 23:22 ` Arjan van de Ven
2007-06-03 1:45 ` Satyam Sharma [this message]
2007-06-01 23:16 Daniel J Blueman
[not found] <12467610.159201180797054019.JavaMail.root@jupiler.digium.com>
2007-06-02 15:12 ` Matt Fredrickson
2007-06-03 11:22 ` Daniel J Blueman
[not found] <17916027.160971180851607681.JavaMail.root@jupiler.digium.com>
2007-06-03 6:20 ` Matt Fredrickson
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=a781481a0706021845y2fd8442fy388c0df58aabcedc@mail.gmail.com \
--to=satyam.sharma@gmail.com \
--cc=arjan@infradead.org \
--cc=creslin@digium.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®