All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Kanaka Juvva <kanaka.d.juvva@intel.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Kanaka Juvva <kanaka.d.juvva@linux.intel.com>,
	"Williamson, Glenn P" <glenn.p.williamson@intel.com>,
	"Auld, Will" <will.auld@intel.com>,
	Andi Kleen <andi@firstfloor.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	Peter Zijlstra <peterz@infradead.org>, Tejun Heo <tj@kernel.org>,
	"x86@kernel.org" <x86@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Shivappa, Vikas" <vikas.shivappa@intel.com>
Subject: Re: [PATCH v3 1/2] perf,x86: add Intel Memory Bandwidth Monitoring (MBM) PMU
Date: Fri, 11 Sep 2015 22:11:17 +0100	[thread overview]
Message-ID: <20150911211117.GB2537@codeblueprint.co.uk> (raw)
In-Reply-To: <1441919929.8892.10.camel@intel.com>

On Thu, 10 Sep, at 02:18:49PM, Kanaka Juvva wrote:
> > > 
> > > > >         } else {
> > > > >                 mbm_current = &mbm_total[vrmid];
> > > > >                 eventid     = QOS_MBM_TOTAL_EVENT_ID;
> > > > >         }
> > > > >         rmid = tmp32;
> > > > 
> > > > Why did you assign rmid to vrmid if you reassign it before it was used?
> > > > 
> > > > 
> > > 
> > > For MSR writes we use rmid value and for mbm_* arrary we use vrmid which is actual
> > > index.
> > 
> > What I'm saying is that the assignment rmid = vrmid looks unnecessary in
> > this piece of code.
> > 
> 
> From my previous review:
> 
>   "This is completely backwards.
>  
>         tmp32 = rmid;  
>         rmid = vrmid;
>         do_stuff(rmid);
>         rmid = tmp32;
>         do_other_stuff(rmid);
> 
>    Why can't you use vrmid for do_stuff() and leave rmid alone? Just
>    because it would make the code simpler to read?"
> 
> I have included Thomas comment inline above.
> 
> and also I meant the following logic:
> 
> writemsr(..,rmid,...)
> mbm_*[vrmid]  
> 
> So new patch will use this logic.
 
OK, let's pull the code in and discuss this with some context,

	u64 val, currentmsr, currentbw, diff_time, cma, bytes, index;                                                                                                                      
        bool overflow = false, first = false;
        ktime_t cur_time;
        u32 tmp32 = rmid, eventid;
        struct sample *mbm_current;
        u32 vrmid = rmid_2_index(rmid);
 
        rmid = vrmid;			<--------- This looks wrong
        cur_time = ktime_get();
        if (read_mbm_local) {
                mbm_current = &mbm_local[vrmid];
                eventid     =  QOS_MBM_LOCAL_EVENT_ID_HW;
                wrmsr(MSR_IA32_QM_EVTSEL, QOS_MBM_LOCAL_EVENT_ID_HW, rmid);	<---- Unneccesary because..
        } else {
                mbm_current = &mbm_total[vrmid];
                eventid     = QOS_MBM_TOTAL_EVENT_ID;
        }
        rmid = tmp32;
        wrmsr(MSR_IA32_QM_EVTSEL, eventid, rmid);	<----- ... you write here
 
So you don't actually use 'rmid' within that if/else block. You can
probably get away with deleting 'tmp32' now that you've refactored
things.

-- 
Matt Fleming, Intel Open Source Technology Center

  reply	other threads:[~2015-09-11 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-08  6:42 [PATCH v3 1/2] perf,x86: add Intel Memory Bandwidth Monitoring (MBM) PMU Kanaka Juvva
2015-08-16 17:42 ` Juvva, Kanaka D
2015-08-19 20:50 ` Thomas Gleixner
2015-08-20 21:54   ` Juvva, Kanaka D
2015-08-21 12:30     ` Thomas Gleixner
     [not found]   ` <06033C969873E840BDE9FC9B584F66B51944F51B@ORSMSX116.amr.corp.intel.com>
2015-09-08 11:47     ` Matt Fleming
2015-09-08 16:11       ` Juvva, Kanaka D
2015-09-08 17:06       ` Juvva, Kanaka D
2015-09-10 13:58         ` Matt Fleming
2015-09-10 21:18           ` Kanaka Juvva
2015-09-11 21:11             ` Matt Fleming [this message]
2015-09-08 19:57       ` [PATCH v3 1/2] perf, x86: " kanaka.d.juvva

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=20150911211117.GB2537@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=andi@firstfloor.org \
    --cc=glenn.p.williamson@intel.com \
    --cc=hpa@zytor.com \
    --cc=kanaka.d.juvva@intel.com \
    --cc=kanaka.d.juvva@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=vikas.shivappa@intel.com \
    --cc=will.auld@intel.com \
    --cc=x86@kernel.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.