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: [PATCHv2 for soc 3/4] arm: Add v7_invalidate_l1 to cache-v7.S
Date: Fri, 1 Feb 2013 11:32:33 +0000	[thread overview]
Message-ID: <20130201113233.GJ23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <510BA728.4060300@ti.com>

On Fri, Feb 01, 2013 at 04:59:44PM +0530, Santosh Shilimkar wrote:
> Now since we are moving the code under common place, probably we should
> update this a function a bit so that it invalidates the CPU cache till
> line of unification. Just to be consistent with other flush API.

Hmm.  Do you really want a CPU being brought up to do that to the PoU,
every time that it is brought up?  I thought you wanted to get rid of
that kind of stuff from the hotplug paths so that a CPU being brought
up/taken down doesn't affect the caches for the other CPUs within the
inner sharable domain.

  reply	other threads:[~2013-02-01 11:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 17:05 [PATCHv2 for soc 0/4] Enabling socfpga on hardware dinguyen at altera.com
2013-01-31 17:05 ` [PATCHv2 for soc 1/4] arm: socfpga: Add new device tree source for actual socfpga HW dinguyen at altera.com
2013-02-01  3:46   ` Olof Johansson
2013-02-01 15:23     ` Dinh Nguyen
2013-01-31 17:05 ` [PATCHv2 for soc 2/4] arm: socfpga: Add entries to enable make dtbs socfpga dinguyen at altera.com
2013-01-31 17:05 ` [PATCHv2 for soc 3/4] arm: Add v7_invalidate_l1 to cache-v7.S dinguyen at altera.com
2013-01-31 18:11   ` Stephen Warren
2013-02-01  3:47   ` Olof Johansson
2013-02-01 11:29   ` Santosh Shilimkar
2013-02-01 11:32     ` Russell King - ARM Linux [this message]
2013-02-01 11:44       ` Santosh Shilimkar
2013-02-01 12:48         ` Russell King - ARM Linux
2013-02-01 13:04           ` Santosh Shilimkar
2013-02-01 13:20             ` Russell King - ARM Linux
2013-02-01 14:09               ` Santosh Shilimkar
2013-02-01 12:11     ` Lorenzo Pieralisi
2013-02-01 12:24       ` Santosh Shilimkar
2013-02-01 12:54       ` Russell King - ARM Linux
2013-02-01 14:10         ` Lorenzo Pieralisi
2013-02-01 14:19           ` Russell King - ARM Linux
2013-02-01 14:31             ` Russell King - ARM Linux
2013-02-01 14:43               ` Santosh Shilimkar
2013-02-01 14:49                 ` Russell King - ARM Linux
2013-02-01 14:53                   ` Santosh Shilimkar
2013-02-01 14:34             ` Lorenzo Pieralisi
2013-01-31 17:05 ` [PATCHv2 for soc 4/4] arm: socfpga: Add SMP support for actual socfpga harware dinguyen at altera.com
2013-02-01  3:50   ` Olof Johansson
2013-02-01 10:46     ` Pavel Machek
2013-02-01 15:27       ` Dinh Nguyen
2013-02-01 15:31         ` Russell King - ARM Linux
2013-02-01 16:39           ` Dinh Nguyen
2013-02-02 19:24             ` Pavel Machek
2013-02-02 21:37               ` Dinh Nguyen
2013-02-03 18:36                 ` Pavel Machek
2013-02-04 16:12                   ` Dinh Nguyen
2013-02-01 10:50   ` Pavel Machek

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=20130201113233.GJ23505@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).