mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Imre Kaloz" <kaloz@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] MIPS: sgi-ip32: Fence PIO reads on CRIME 1.1
Date: Wed, 11 Nov 2026 11:10:03 +0100	[thread overview]
Message-ID: <7b19087a-986a-414c-a35c-e44052458495@app.fastmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2611080926150.17804@angie.orcam.me.uk>

On Sun, Nov 8, 2026, at 10:28, Maciej W. Rozycki wrote:
> On Sat, 7 Nov 2026, Imre Kaloz wrote:

<snip>

>> +static inline void plat_read_fence_end(unsigned long flags)
>> +{
>> +	crime_read_fence_end(flags);
>> +}
>
>  This seems hackish to me with the call to local_irq_restore() buried in 
> crime_read_fence_end().  Why is is out of line?

Good point, thanks.  Only the 5us udelay() needs to be out of line,
so that asm/io.h does not have to pull in linux/delay.h, the irq
restore had no business being buried in there with it.

v3 keeps local_irq_save() and local_irq_restore() together in
read-fence.h and makes only crime_read_fence_delay() out of line.

It has been retested on a CRIME 1.1 O2 with audio and SCSI DMA
running: 0 stale reads in 50M read pairs with the fence on, 15 in 10M
with it off.


Thanks,
Imre

P.S:
v3: https://lore.kernel.org/r/20261111095650.14954-1-kaloz@kernel.org/

      reply	other threads:[~2026-11-11 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  0:52 Imre Kaloz
2026-11-08  9:28 ` Maciej W. Rozycki
2026-11-11 10:10   ` Imre Kaloz [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=7b19087a-986a-414c-a35c-e44052458495@app.fastmail.com \
    --to=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=tsbogend@alpha.franken.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 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®