All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Matt Redfearn <Matt.Redfearn@imgtec.com>,
	Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	James Hogan <James.Hogan@imgtec.com>,
	Paul Burton <Paul.Burton@imgtec.com>,
	Raghu Gandham <Raghu.Gandham@imgtec.com>,
	Douglas Leung <Douglas.Leung@imgtec.com>,
	Petar Jovanovic <Petar.Jovanovic@imgtec.com>,
	Miodrag Dinic <Miodrag.Dinic@imgtec.com>,
	Goran Ferenc <Goran.Ferenc@imgtec.com>
Subject: Re: [PATCH 3/8] MIPS: R6: Fix PREF instruction usage by memcpy for MIPS R6
Date: Wed, 28 Jun 2017 03:36:54 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1706280329280.31404@tp.orcam.me.uk> (raw)
In-Reply-To: <9915e476-70fe-4281-a1e4-85ca2e8683b3@imgtec.com>

On Wed, 28 Jun 2017, Leonid Yegoshin wrote:

> The bigger problem is a prefetch overrun to device registers. AT use is just
> nuisance.

 That isn't however what the patch addresses, not at least according to 
the description provided.

 How far beyond the data copied do we prefetch anyway, and can't we simply 
waste a page's worth of space or so at the physical end of each RAM area 
present in a given system?  Or perhaps use it for something we know for 
sure that won't ever be copied.

  Maciej

  parent reply	other threads:[~2017-06-28  2:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 15:50 [PATCH 0/8] MIPS: Miscellaneous fixes related to Android Mips emulator Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 1/8] MIPS: cmdline: Add support for 'memmap' parameter Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 2/8] MIPS: build: Fix "-modd-spreg" switch usage when compiling for mips32r6 Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 3/8] MIPS: R6: Fix PREF instruction usage by memcpy for MIPS R6 Aleksandar Markovic
2017-06-20  8:04   ` Matt Redfearn
2017-06-20  8:04     ` Matt Redfearn
2017-06-28  0:58     ` Ralf Baechle
2017-06-28  1:35       ` Maciej W. Rozycki
2017-06-28  1:35         ` Maciej W. Rozycki
     [not found]         ` <9915e476-70fe-4281-a1e4-85ca2e8683b3@imgtec.com>
2017-06-28  2:36           ` Maciej W. Rozycki [this message]
2017-06-28  8:34             ` Ralf Baechle
2017-06-28 11:23               ` Maciej W. Rozycki
2017-06-19 15:50 ` [PATCH 4/8] MIPS: unaligned: Add DSP lwx & lhx missaligned access support Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 5/8] MIPS: math-emu: Handle zero accumulator case in MADDF and MSUBF separately Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 6/8] input: goldfish: Fix multitouch event handling Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 7/8] tty: goldfish: Use streaming DMA for r/w operations on Ranchu platforms Aleksandar Markovic
2017-06-19 15:50 ` [PATCH 8/8] tty: goldfish: Implement support for kernel 'earlycon' parameter Aleksandar Markovic

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=alpine.DEB.2.00.1706280329280.31404@tp.orcam.me.uk \
    --to=macro@imgtec.com \
    --cc=Douglas.Leung@imgtec.com \
    --cc=Goran.Ferenc@imgtec.com \
    --cc=James.Hogan@imgtec.com \
    --cc=Leonid.Yegoshin@imgtec.com \
    --cc=Matt.Redfearn@imgtec.com \
    --cc=Miodrag.Dinic@imgtec.com \
    --cc=Paul.Burton@imgtec.com \
    --cc=Petar.Jovanovic@imgtec.com \
    --cc=Raghu.Gandham@imgtec.com \
    --cc=aleksandar.markovic@rt-rk.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.