Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: Kevin Cernekee <cernekee@chromium.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH V2 1/3] MIPS: Fix cache flushing for swap pages with non-DMA I/O.
Date: Tue, 24 Feb 2015 10:20:59 -0600	[thread overview]
Message-ID: <54ECA4EB.6010807@imgtec.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1502240217360.17311@eddie.linux-mips.org>

On 02/23/2015 08:24 PM, Maciej W. Rozycki wrote:
> On Mon, 23 Feb 2015, Leonid Yegoshin wrote:
> 
>> The same is basically for transfer D$ --> I$ because in MIPS it is done via L2
>> or memory.
> 
>  The original issue aside (I don't want to dive into it) this I believe is 
> left to an implementer's discretion and there are MIPS implementations 
> indeed that fill I$ directly from D$; IIRC Alchemy silicon and its 
> descendants.
> 
>   Maciej
> 
I am tracking down even more HIGHMEM bugs, so I will rework these
patches, clean-up commit messages and post again. Thanks for all the
feedback.

Steve

  parent reply	other threads:[~2015-02-24 16:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 16:17 [PATCH V2 0/3] HIGHMEM and cache flush fixes Steven J. Hill
2015-02-19 16:17 ` Steven J. Hill
2015-02-19 16:17 ` [PATCH V2 1/3] MIPS: Fix cache flushing for swap pages with non-DMA I/O Steven J. Hill
2015-02-19 16:17   ` Steven J. Hill
2015-02-20 19:17   ` Kevin Cernekee
2015-02-24  0:56     ` Leonid Yegoshin
2015-02-24  0:56       ` Leonid Yegoshin
2015-02-24  1:13       ` Zenon Fortuna
2015-02-24  1:13         ` Zenon Fortuna
2015-02-24  2:33         ` Maciej W. Rozycki
2015-02-24  2:33           ` Maciej W. Rozycki
2015-02-24 21:06           ` Leonid Yegoshin
2015-02-24 21:06             ` Leonid Yegoshin
2015-02-24 21:51             ` Maciej W. Rozycki
2015-02-24 21:51               ` Maciej W. Rozycki
2015-02-24 21:57               ` Leonid Yegoshin
2015-02-24 21:57                 ` Leonid Yegoshin
2015-02-24 22:50                 ` Maciej W. Rozycki
2015-02-24 22:50                   ` Maciej W. Rozycki
2015-02-24 22:57                   ` David Daney
2015-02-24 22:57                     ` David Daney
2015-02-24 23:19                     ` Leonid Yegoshin
2015-02-24 23:19                       ` Leonid Yegoshin
2015-02-24 23:58                       ` David Daney
2015-02-24 23:58                         ` David Daney
2015-02-25  0:07                       ` Maciej W. Rozycki
2015-02-25  0:07                         ` Maciej W. Rozycki
2015-02-25  0:38                         ` David Daney
2015-02-25  0:38                           ` David Daney
2015-02-24 23:15                   ` Leonid Yegoshin
2015-02-24 23:15                     ` Leonid Yegoshin
2015-02-24  2:24       ` Maciej W. Rozycki
2015-02-24  2:24         ` Maciej W. Rozycki
2015-02-24 16:20         ` Steven J. Hill [this message]
2015-02-19 16:17 ` [PATCH V2 2/3] MIPS: Highmem: Fixes for cache aliasing and color Steven J. Hill
2015-02-19 16:17   ` Steven J. Hill
2015-02-19 16:17 ` [PATCH V2 3/3] MIPS: Fix I-cache flushing for kmap'd pages Steven J. Hill
2015-02-19 16:17   ` Steven J. Hill

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=54ECA4EB.6010807@imgtec.com \
    --to=steven.hill@imgtec.com \
    --cc=Leonid.Yegoshin@imgtec.com \
    --cc=cernekee@chromium.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.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