All of lore.kernel.org
 help / color / mirror / Atom feed
From: LaMont Jones <lamont@security.hp.com>
To: Philipp Rumpf <prumpf@suse.de>
Cc: Grant Grundler <grundler@cup.hp.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	parisc-linux@thepuffingroup.com, lamont@security.hp.com
Subject: Re: [parisc-linux] Thoughts on arch/parisc/irq.c
Date: Thu, 26 Aug 1999 10:43:29 -0600	[thread overview]
Message-ID: <19990826164329.DEB9418708@security.hp.com> (raw)
In-Reply-To: Your message of "Thu, 26 Aug 1999 17:26:26 +0200." <19990826172626.K19314@suse.de>

> No.  You just do
> gsc_writel(0xfffe0000 + dev->irq, dev->hpa + DEVICE_SPECIFIC_OFFSET);
> right after request_irq(dev->irq, ...);
> Is it ok with you if we worry about SMP and PA2.0 boxes later ?

Writing to the specific HPA is most likely a SMP issue as well, but if we
go the route of using global broadcast interrupts, we should leave some
__really__ large handwriting on the wall for when SMP gets dealt with.
The mad dash to handle an interrupt is a great way to thrash the machine.

Likewise, if there's a clean way to get the processor HPA in the IRQ value,
there is no reason not to do it now, and avoid tracking down the problems
later.

lamont

  reply	other threads:[~1999-08-26 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37C432D3.C9BC0D7F@thepuffingroup.com>
1999-08-26  0:49 ` [parisc-linux] Thoughts on arch/parisc/irq.c Grant Grundler
1999-08-26  1:16   ` Alan Cox
1999-08-26  2:13     ` Grant Grundler
1999-08-26 12:06       ` Alan Cox
1999-08-26 15:26       ` Philipp Rumpf
1999-08-26 16:43         ` LaMont Jones [this message]
1999-08-26 17:13         ` Grant Grundler
1999-08-26 17:48           ` Alex deVries
1999-08-26 18:12           ` Philipp Rumpf
1999-08-26 15:16   ` Philipp Rumpf
     [not found] <199908261629.JAA12121@milano.cup.hp.com>
1999-08-26 16:38 ` Alan Cox

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=19990826164329.DEB9418708@security.hp.com \
    --to=lamont@security.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=prumpf@suse.de \
    /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.