From: afzal mohammed <afzal.mohd.ma@gmail.com>
To: Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] ia64: replace setup_irq() by request_irq()
Date: Fri, 13 Mar 2020 18:01:41 +0530 [thread overview]
Message-ID: <20200313123141.GA7155@afzalpc> (raw)
In-Reply-To: <20200308120350.19117-1-afzal.mohd.ma@gmail.com>
Hi Tony Luck,
On Sun, Mar 08, 2020 at 05:33:49PM +0530, afzal mohammed wrote:
> request_irq() is preferred over setup_irq(). Invocations of setup_irq()
> occur after memory allocators are ready.
>
> Per tglx[1], setup_irq() existed in olden days when allocators were not
> ready by the time early interrupts were initialized.
>
> Hence replace setup_irq() by request_irq().
>
> Changing 'ia64_native_register_percpu_irq' decleration to include
> 'irq_handler_t' as an argument type in arch/ia64/include/asm/hw_irq.h
> was causing build error - 'unknown type name 'irq_handler_t''
>
> This was due to below header file sequence,
> + include/interrupt.h
> + include/hardirq.h
> + asm/hardirq.h
> + include/irq.h
> + asm/hw_irq.h
> [ 'ia64_native_register_percpu_irq' declared w/ 'irq_handler_t']
> [ 'irq_handler_t' typedef'ed here in 'include/interrupt.h']
>
> 'register_percpu_irq' defined to 'ia64_native_register_percpu_irq' is
> the one invoked by the caller, not the latter directly. This was done
> to support paravirtualization which was removed around 4 years back.
> And 'register_percpu_irq' is invoked only inside 'arch/ia64/kernel'.
>
> So 'register_percpu_irq' define to 'ia64_native_register_percpu_irq' is
> removed, instead 'ia64_native_register_percpu_irq' is renamed to
> 'register_precpu_irq()' & it is directly invoked. Also,
> 'register_precpu_irq()' is declared in a new header file 'irq.h' inside
> 'arch/ia64/kernel/', this header file is included by C files invoking
> 'register_percpu_irq()'.
>
> [1] https://lkml.kernel.org/r/alpine.DEB.2.20.1710191609480.1971@nanos
>
> Signed-off-by: afzal mohammed <afzal.mohd.ma@gmail.com>
Seems you handle pull requests for ia64, if this change is okay, can
please consider taking this thr' your tree ?
Regards
afzal
next prev parent reply other threads:[~2020-03-13 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 0:49 [PATCH v3] ia64: replace setup_irq() by request_irq() afzal mohammed
2020-03-08 12:03 ` [PATCH v4] " afzal mohammed
2020-03-13 12:31 ` afzal mohammed [this message]
2020-03-13 23:28 ` Luck, Tony
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=20200313123141.GA7155@afzalpc \
--to=afzal.mohd.ma@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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