linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Gabriel Paubert <paubert@iram.es>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Latest OpenPic changes
Date: Fri, 11 Feb 2000 19:38:08 +0100	[thread overview]
Message-ID: <20000211193808.018868@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.HPX.4.10.10002111837290.1866-100000@gra-ux1.iram.es>


On Fri, Feb 11, 2000, Gabriel Paubert <paubert@iram.es> wrote:

>If it's truly the case we should consider a different solution. Masking
>interrupts in a device or controller for a very short lapse is dominated
>by the HW access overhead, and this is bad. sync instructions are also
>extremely bad.

I implemented it in both enable and disable for "correctness" so that the
status of the controller is guaranteed when exiting any of those 2
functions. I agree that the unmask case may not be important.

I beleive the sync here can also be completely removed too. A single
eieio is plenty enough because of the read. Isn't it ?

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-02-11 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-11 16:43 Latest OpenPic changes Geert Uytterhoeven
2000-02-11 17:05 ` Benjamin Herrenschmidt
2000-02-11 17:16   ` Geert Uytterhoeven
2000-02-11 17:11 ` Gabriel Paubert
2000-02-11 17:16   ` Geert Uytterhoeven
2000-02-11 17:30     ` Gabriel Paubert
2000-02-11 21:17       ` Cort Dougan
2000-02-11 17:31   ` Benjamin Herrenschmidt
2000-02-11 17:49     ` Gabriel Paubert
2000-02-11 18:38       ` Benjamin Herrenschmidt [this message]
2000-02-11 20:25         ` Gabriel Paubert
2000-02-12 14:15           ` BenH

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=20000211193808.018868@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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;
as well as URLs for NNTP newsgroup(s).