Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] msm: scm: Get cacheline size from CTR
Date: Thu, 24 Feb 2011 20:56:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1102242056010.2701@localhost6.localdomain6> (raw)
In-Reply-To: <4D66B505.6010702@codeaurora.org>

On Thu, 24 Feb 2011, Stephen Boyd wrote:

> On 02/24/2011 11:01 AM, Thomas Gleixner wrote:
> > On Thu, 24 Feb 2011, Stephen Boyd wrote:
> >
> >>
> >>  /**
> >>   * scm_call() - Send an SCM command
> >>   * @svc_id: service identifier
> >> @@ -243,11 +248,13 @@ int scm_call(u32 svc_id, u32 cmd_id, const void *cmd_buf, size_t cmd_len,
> >>  	do {
> >>  		u32 start = (u32)rsp;
> >>  		u32 end = (u32)scm_get_response_buffer(rsp) + resp_len;
> >> -		start &= ~(CACHELINESIZE - 1);
> >> +		u32 cacheline_size = dcache_line_size();
> >
> > And why do you want to do that on every scm_call() invocation and on
> > every loop of that code? If your dcache_line_size() changes at
> > runtime, then you might have other problems.
> 
> I definitely don't want to do it for every loop. I'm fine with getting
> it every scm_call() invocation though.
> 
> For now, I'll pull the end and cacheline_size variables out of the
> do-while loop.

Why not do it correct right away and retrieve it in an __init
function?

Thanks,

	tglx

  reply	other threads:[~2011-02-24 19:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 18:44 [PATCH 0/4] SCM fixes and updates Stephen Boyd
2011-02-24 18:44 ` [PATCH 1/4] msm: scm: Mark inline asm as volatile Stephen Boyd
2011-02-25 11:56   ` Will Deacon
2011-02-25 19:05     ` Stephen Boyd
2011-02-26 18:12     ` David Brown
2011-02-26 19:43       ` Nicolas Pitre
2011-02-27 17:41         ` David Brown
2011-02-28  2:21           ` Nicolas Pitre
2011-02-27 11:10       ` Will Deacon
2011-02-27 17:38         ` David Brown
2011-03-01 10:30           ` Will Deacon
2011-02-24 18:44 ` [PATCH 2/4] msm: scm: Fix improper register assignment Stephen Boyd
2011-02-25 13:23   ` Will Deacon
2011-02-25 19:22     ` Stephen Boyd
2011-02-26  5:09     ` Saravana Kannan
2011-02-26  8:47       ` Russell King - ARM Linux
2011-02-26 17:58         ` David Brown
2011-02-26 20:04           ` Nicolas Pitre
2011-03-01 10:37             ` Will Deacon
2011-03-01 21:29               ` Saravana Kannan
2011-03-02  0:02                 ` Nicolas Pitre
2011-03-01 13:54             ` Will Deacon
2011-02-24 18:44 ` [PATCH 3/4] msm: scm: Check for interruption immediately Stephen Boyd
2011-02-24 18:44 ` [PATCH 4/4] msm: scm: Get cacheline size from CTR Stephen Boyd
2011-02-24 19:01   ` Thomas Gleixner
2011-02-24 19:44     ` Stephen Boyd
2011-02-24 19:56       ` Thomas Gleixner [this message]
2011-03-01  4:21         ` Stephen Boyd
2011-02-24 19:32   ` Sergei Shtylyov
2011-02-24 19:50     ` Stephen Boyd
2011-02-24 19:55     ` Russell King - ARM Linux
2011-03-09 19:29 ` [PATCH 0/4] SCM fixes and updates Stephen Boyd
2011-03-10 20:06   ` David Brown

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.LFD.2.00.1102242056010.2701@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --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