historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nelson D'Souza <nelson.dsouza@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Fwd: [PATCH 4/4] walnut 4
Date: Fri, 22 Feb 2019 15:19:57 -0800	[thread overview]
Message-ID: <8d61c52d-b55c-aec5-ab47-4f9c6dc4cb6f@linux.intel.com> (raw)
In-Reply-To: <47f2b71e-96b5-da80-d87e-882b36a34133@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 562 bytes --]



Hi Peter,

I have attached the initial test logs from your latest patchset. 

The perf command does not crash when /sys/devices/cpu/allow_tsx_force_abort is set to 0.
 
Thanks,
Nelson

On 2/19/19 8:10 AM, speck for Peter Zijlstra wrote:
> On Tue, Feb 19, 2019 at 04:58:11PM +0100, speck for Peter Zijlstra wrote:
>> +	if (!allow_tsx_force_abort && test_bit(3, c->idxmsk)) {
>> +		c = dyn_constraint(cpuc, c, idx);
>> +		c->idxmsk64 &= ~(1ULL << 3);
>> +		c->weight = c->idxmsk64 - 1;
> 
> Damn; that should be:
> 
> 		c->weight--;
> 



[-- Attachment #1.2: tsx_force_abort_0.3counters --]
[-- Type: text/plain, Size: 399 bytes --]

# started on Thu Feb 21 15:23:52 2019


 Performance counter stats for 'system wide':

            89,033      cache-misses              #   21.591 % of all cache refs    
           412,353      cache-references                                            
     4,630,472,209      branches                                                    

       1.005154418 seconds time elapsed




[-- Attachment #1.3: tsx_force_abort_0.4counters --]
[-- Type: text/plain, Size: 485 bytes --]

# started on Thu Feb 21 15:24:10 2019


 Performance counter stats for 'system wide':

     <not counted>      cache-misses                                                
     <not counted>      cache-references                                            
     <not counted>      branches                                                    
   <not supported>      branch-misses                                               

       1.005054423 seconds time elapsed




[-- Attachment #1.4: tsx_force_abort_1.3counters --]
[-- Type: text/plain, Size: 399 bytes --]

# started on Thu Feb 21 15:21:37 2019


 Performance counter stats for 'system wide':

            58,484      cache-misses              #   14.165 % of all cache refs    
           412,875      cache-references                                            
     4,627,163,916      branches                                                    

       1.005123883 seconds time elapsed




[-- Attachment #1.5: tsx_force_abort_1.4counters --]
[-- Type: text/plain, Size: 485 bytes --]

# started on Thu Feb 21 15:21:04 2019


 Performance counter stats for 'system wide':

            71,146      cache-misses              #   11.203 % of all cache refs    
           635,039      cache-references                                            
     4,616,150,556      branches                                                    
            84,552      branch-misses             #    0.00% of all branches        

       1.005141562 seconds time elapsed




  reply	other threads:[~2019-02-22 23:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 15:58 [MODERATED] [PATCH 0/4] walnut 0 Peter Zijlstra
2019-02-19 15:58 ` [MODERATED] [PATCH 1/4] walnut 1 Peter Zijlstra
2019-02-19 15:58 ` [MODERATED] [PATCH 2/4] walnut 2 Peter Zijlstra
2019-02-19 15:58 ` [MODERATED] [PATCH 3/4] walnut 3 Peter Zijlstra
2019-02-19 15:58 ` [MODERATED] [PATCH 4/4] walnut 4 Peter Zijlstra
2019-02-19 16:10   ` [MODERATED] " Peter Zijlstra
2019-02-20 22:31     ` Nelson D'Souza
2019-02-22 22:58       ` [MODERATED] Fwd: " Nelson D'Souza
2019-02-22 23:19         ` Nelson D'Souza [this message]
2019-02-19 18:49   ` [MODERATED] Linus Torvalds
2019-02-20 14:37     ` Peter Zijlstra
2019-03-07 13:56   ` [MODERATED] Re: [PATCH 4/4] walnut 4 Greg KH
2019-03-07 14:34     ` Peter Zijlstra
2019-03-07 15:09     ` mark gross
2019-02-20 18:10 ` [MODERATED] Re: [PATCH 0/4] walnut 0 mark gross
2019-02-22 19:20   ` Nelson D'Souza
2019-03-01 18:59 ` mark gross

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=8d61c52d-b55c-aec5-ab47-4f9c6dc4cb6f@linux.intel.com \
    --to=nelson.dsouza@linux.intel.com \
    --cc=speck@linutronix.de \
    /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).