mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bryan Rittmeyer <bryanr@bryanr.org>
Cc: oprofile-list@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [patch] oprofile + ppc750cx perfmon
Date: 25 Mar 2003 10:45:02 +0100	[thread overview]
Message-ID: <1048585501.581.16.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030325085759.GB30294@bryanr.org>

On Tue, 2003-03-25 at 09:57, Bryan Rittmeyer wrote:

> wow. inside of open_pic.c, I bet it's code like this
> 
>         while (openpic_read(addr) & OPENPIC_ACTIVITY);
> 
> that's showing up.

That's interesting. You are raising again an old debate of
wether to disable the IRQ during handling on openpic or not,
I beleive we don't need to disable it on this PIC, but we
do this for "safety" reasons.

In fact, I think our

openpic_ack_irq() should do something like

  if (edge)
	openpic_eoi();

and our openpic_end_irq() something like

  if (level)
	openpic_eoi();

Also, the fact that PIC access is slow is a generic "feature"
of such chips, I also think we could actually be smarter and only
soft-disable IRQs with a flag in the descriptor, and hard disable
them if and only if they actually occur while disabled.

Ben.


  reply	other threads:[~2003-03-25  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25  5:09 Bryan Rittmeyer
2003-03-25  8:57 ` Bryan Rittmeyer
2003-03-25  9:45   ` Benjamin Herrenschmidt [this message]
2003-03-26  5:04     ` Bryan Rittmeyer
     [not found]   ` <20030325174309.GB57374@compsoc.man.ac.uk>
2003-03-26  3:50     ` Bryan Rittmeyer
     [not found]       ` <20030327010121.GA94874@compsoc.man.ac.uk>
2003-03-28  8:50         ` Bryan Rittmeyer
     [not found] <20030327130535.GA1132@bryanr.org>
     [not found] ` <F0BBB858-6093-11D7-BD8D-000393C30512@motorola.com>
2003-03-28  8:31   ` Bryan Rittmeyer

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=1048585501.581.16.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=bryanr@bryanr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=oprofile-list@lists.sourceforge.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

all inboxes | Powered by JetHome®