public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Nerín" <jnerin@juridicas.com>
To: Jaswinder Singh <jaswinder.singh@3disystems.com>
Cc: Randy <randys@evcom.net>, linux-kernel@vger.kernel.org
Subject: Re: CPU Dedicated Interrupts
Date: Mon, 28 May 2001 13:28:08 +0200	[thread overview]
Message-ID: <3B123648.9080707@juridicas.com> (raw)
In-Reply-To: <3B0FBF11.21EB8F87@evcom.net> <00be01c0e71e$49840d80$52a6b3d0@Toshiba>

Jaswinder Singh wrote:

>> What is the easiest way to tell a CPU to ignore certain interrupts from
>> module?
>> Is there an IRQ mask for each processor? Is that symbol exported?
>> 
> 
> I also what to know this :)
> 
> Please help us .
> 
> Thank you.
> 
> Jaswinder.
> --
> These are my opinions not 3Di.
> 
It's not a symbol, look for info about /proc/[irq-number]/smp_affinity 
in /Documentation.

-- 
Jorge Nerin
<comandante@zaralinux.com>


      reply	other threads:[~2001-05-28 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-26 14:34 CPU Dedicated Interrupts Randy
2001-05-28  2:31 ` Jaswinder Singh
2001-05-28 11:28   ` Jorge Nerín [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=3B123648.9080707@juridicas.com \
    --to=jnerin@juridicas.com \
    --cc=comandante@zaralinux.com \
    --cc=jaswinder.singh@3disystems.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randys@evcom.net \
    /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