Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Sven Schnelle <svens@stackframe.org>, <linux-mips@linux-mips.org>
Subject: Re: MIPS: MIPS74K needs post dma flush
Date: Mon, 7 Nov 2016 12:06:18 -0800	[thread overview]
Message-ID: <5820DEBA.6080800@imgtec.com> (raw)
In-Reply-To: <20161107194128.25086-2-svens@stackframe.org>

74K does NOT have an aggressive speculation, never for D-Cache, never 
for I-cache. D-Cache doesn't an advance speculation load at all, I-cache 
never does a wrong speculation.

So, post-DMA flush is not needed in any form.

- Leonid.

WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Sven Schnelle <svens@stackframe.org>, linux-mips@linux-mips.org
Subject: Re: MIPS: MIPS74K needs post dma flush
Date: Mon, 7 Nov 2016 12:06:18 -0800	[thread overview]
Message-ID: <5820DEBA.6080800@imgtec.com> (raw)
Message-ID: <20161107200618.SI_iWWeT_3ByNsQQRTPVlMxwf14Buw9FB1oF7WNWazY@z> (raw)
In-Reply-To: <20161107194128.25086-2-svens@stackframe.org>

74K does NOT have an aggressive speculation, never for D-Cache, never 
for I-cache. D-Cache doesn't an advance speculation load at all, I-cache 
never does a wrong speculation.

So, post-DMA flush is not needed in any form.

- Leonid.

  reply	other threads:[~2016-11-07 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 19:41 MIPS74K dma coherence issue Sven Schnelle
2016-11-07 19:41 ` [PATCH] MIPS: MIPS74K needs post dma flush Sven Schnelle
2016-11-07 20:06   ` Leonid Yegoshin [this message]
2016-11-07 20:06     ` Leonid Yegoshin

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=5820DEBA.6080800@imgtec.com \
    --to=leonid.yegoshin@imgtec.com \
    --cc=linux-mips@linux-mips.org \
    --cc=svens@stackframe.org \
    /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