linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: l2c: add options to overwrite prefetching behavior
Date: Thu, 11 Jun 2015 10:34:17 +0100	[thread overview]
Message-ID: <20150611093417.GV7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150611112459.6590ab05@free-electrons.com>

On Thu, Jun 11, 2015 at 11:24:59AM +0200, Thomas Petazzoni wrote:
> Dear Hauke Mehrtens,
> 
> On Wed, 10 Jun 2015 21:26:35 +0200, Hauke Mehrtens wrote:
> 
> > Thanks for asking, I did not know Russell's patch process, but Florian
> > guided me and now it is submitted, see
> > http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8391/1
> 
> I tested your patch, and I'm not sure how it can work for you, because
> the changes made to the PREFETCH_CTRL register on the data/instruction
> prefetch bits are later overridden by changes made to the AUX_CTRL
> register.

There's also a patch I sent on May 14th which needs to be applied for this
to work, and fixes the above.

> How does your patch handles the fact that the prefetch data and
> prefetch instr are cloned between PREFETCH_CTRL and AUX_CTRL ?

It needs my patch.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-06-11  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 23:19 [PATCH v4] ARM: l2c: add options to overwrite prefetching behavior Hauke Mehrtens
2015-06-10 15:21 ` Thomas Petazzoni
2015-06-10 19:26   ` Hauke Mehrtens
2015-06-11  7:26     ` Thomas Petazzoni
2015-06-11  9:24     ` Thomas Petazzoni
2015-06-11  9:34       ` Russell King - ARM Linux [this message]
2015-06-11  9:39         ` Russell King - ARM Linux
2015-06-11  9:47           ` Thomas Petazzoni
2015-06-10 16:57 ` Florian Fainelli

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=20150611093417.GV7557@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).