From: george anzinger <george@mvista.com>
To: arun4linux <arun4linux@indiatimes.com>,
John K Luebs <jkluebs@luebsphoto.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: switching to interrupt contex when no interrupts
Date: Sun, 24 Nov 2002 08:48:03 -0800 [thread overview]
Message-ID: <3DE102C3.4975BF4F@mvista.com> (raw)
In-Reply-To: 3DE09E60.407FE8D6@mvista.com
george anzinger wrote:
>
> arun4linux wrote:
> >
> > Hello,
> >
> > <<One is forced to run in interrupt context in an
> > interrupt handler.
> > >>Yes. But my requirement is to force my code to run in interrupt context.
> >
> > <<Possibility is undefined here because what you said makes no sense.
> >
> > You will get a better answer from the list if you describe what you are trying to do (in concrete terms), not how you think you might do it.
> >
> > >>My requirement is to simulate a PCI based controller and its behaviour in software. I knew the different type of interrupts and the timings my device produces.
> >
> > I need to simulate this PCI device, its interrupts in sequence and I have to process them in my driver software.
> >
> > Hope this make sense now.
> >
> > Anyway, my requrirement is to simulate the interrupts and process them in the interrupt context.
> >
> > It would be helpful, if anyone could help me how to do it.
> > My idea is to use task queues and bottom halves for this. But I'd like to get clarified on simulating interrupts (rasing the process/task context to interrupt context) and its consequences.
> >
> Why simulate the interrupts when you can just program them?
> On the x86 machine the "int x" instruction generates an
> interrupt to irq "x"+32. You do need to be in kernel land
> to do this, but then I assume that is not a problem.
Uh, make that "x"-32, i.e. "int 34" give irq 2.
-g
>
> -g
>
> >
> > Thanks & Warm Regards
> > Arun
> >
> > "John K Luebs" wrote:
> >
> > On Sat, Nov 23, 2002 at 07:37:33AM +0530, arun4linux wrote:
> > > Hello,
> > >
> > > I'd like to force my kernel module to run at interrupt context at some specific points/time and then come back from interrrupt contex after executing that particular portion of code..
> >
> > You seem to be over complexifying what interrupt context is. It is
> > simply a generic term for a context that executes on account of an
> > architecture interrupt. One is forced to run in interrupt context in an
> > interrupt handler.
> >
> > You "run" in interrupt context by calling request_irq attached to the
> > interrupt line that you are interested in installing a handler for.
> >
> > >
> > > Is it possible?
> >
> > Possibility is undefined here because what you said makes no sense.
> >
> > You will get a better answer from the list if you describe what you are
> > trying to do (in concrete terms), not how you think you might do it.
> >
> > Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
> >
> > Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> George Anzinger george@mvista.com
> High-res-timers:
> http://sourceforge.net/projects/high-res-timers/
> Preemption patch:
> http://www.kernel.org/pub/linux/kernel/people/rml
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2002-11-24 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 19:57 Re: switching to interrupt contex when no interrupts arun4linux
2002-11-24 9:39 ` george anzinger
2002-11-24 16:48 ` george anzinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 12:30 arun4linux
2003-01-02 16:30 ` george anzinger
2002-11-23 2:07 arun4linux
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=3DE102C3.4975BF4F@mvista.com \
--to=george@mvista.com \
--cc=arun4linux@indiatimes.com \
--cc=jkluebs@luebsphoto.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 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.