All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Russell Johnson <russell.johnson@kratosdefense.com>
Cc: xenomai@xenomai.org
Subject: Re: Realtime interrupt handling in driver
Date: Wed, 23 Feb 2022 09:12:17 +0100	[thread overview]
Message-ID: <87h78qf0qe.fsf@xenomai.org> (raw)
In-Reply-To: <PH1P110MB1050BF72127DFC0CE3440B64E23C9@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM>


Russell Johnson via Xenomai <xenomai@xenomai.org> writes:

> Hello,
>
> In my driver that I have been converting to support OOB functionality
> with the EVL core, I have an interrupt handler that handles all
> interrupts from a device sitting on the PCIe bus. I was reading
> through the information on your wiki about interrupt pipelining in
> Dovetail. I was confused a bit on if there is work that I need to do
> in order to get interrupts & interrupt handlers to run out-of-band
> (and not be preempted by in-band linux processing), or if the EVL core
> takes care of that for me?
> If there is work I need to do with
> interrupt config & interrupt handlers in order to make them able to
> run out-of-band, where do I need to start?
>
> Thanks!
>
> Russell

[1] describes the general flow, this is a bit outdated starting from the
upcoming kernel v5.17 series [2], but the logic remains the same though.
[3] explains why and how to fix up the irqchip handlers for IRQ
pipelining.

[1] https://evlproject.org/dovetail/porting/irqflow/
[2] https://source.denx.de/Xenomai/xenomai4/linux-evl/-/tree/v5.17-evl-rebase
[3] https://evlproject.org/dovetail/pipeline/irq_handling/

-- 
Philippe.


      parent reply	other threads:[~2022-02-23  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23  0:10 Realtime interrupt handling in driver Russell Johnson
2022-02-23  6:12 ` Chen, Hongzhan
2022-02-23  8:12 ` Philippe Gerum [this message]

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=87h78qf0qe.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=russell.johnson@kratosdefense.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.