From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Fix percpu interrupt allocation in mmtimer code
Date: Thu, 16 Mar 2006 11:02:34 +0000 [thread overview]
Message-ID: <yq0oe06veid.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20060315143906.GE29195@sgi.com>
>>>>> "Dimitri" = Dimitri Sivanich <sivanich@sgi.com> writes:
Dimitri> The timer interrupt in the mmtimer code needs to be allocated
Dimitri> as a percpu interrupt for acceptable performance on larger
Dimitri> systems.
Dimitri> The code needs to be updated to set this up properly, as the
Dimitri> SA_PERCPU_IRQ flag to request_interrupt is not supported.
Dimitri> +EXPORT_SYMBOL(register_percpu_irq);
Hi Dimitri,
EXPORT_SYMBOL_GPL() please.
Dimitri> +static irqreturn_t mmtimer_interrupt(int irq, void *dev_id, struct pt_regs *regs);
Dimitri> +
The prototype needs to go into a header file, it shouldn't be declared
in mmtimer.c. Also please make sure it doesn't exceed the 80 column
limit.
Cheers,
Jes
next prev parent reply other threads:[~2006-03-16 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 14:39 [PATCH] Fix percpu interrupt allocation in mmtimer code Dimitri Sivanich
2006-03-16 11:02 ` Jes Sorensen [this message]
2006-03-16 15:56 ` Christoph Hellwig
2006-03-16 16:01 ` Dimitri Sivanich
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=yq0oe06veid.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=linux-ia64@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