public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert Schöne" <robert.schoene@tu-dresden.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Prarit Bhargava <prarit@redhat.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Saravana Kannan <skannan@codeaurora.org>
Subject: Re: [PATCH 1/2] cpufreq: serialize calls to __cpufreq_governor()
Date: Fri, 10 Oct 2014 16:05:26 +0200	[thread overview]
Message-ID: <1412949926.13463.47.camel@x200t> (raw)
In-Reply-To: <CAKohpokag-ppE7WH=jPS6-i_T-5PyaDKyKS8uC+Xt2QGxLHYkw@mail.gmail.com>

@all:
I have to leave now and will not be available for a week.

@Viresh:
The line you are looking for is 2c8 (260h+68h, length check passed).
Here it is with the surrounding instructions:


static inline void __gov_queue_work(int cpu, struct dbs_data *dbs_data,
                unsigned int delay)
{
        struct cpu_dbs_common_info *cdbs = dbs_data->cdata->get_cpu_cdbs(cpu);
 2c0:   49 8b 06                mov    (%r14),%rax
 2c3:   89 df                   mov    %ebx,%edi
 2c5:   ff 50 20                callq  *0x20(%rax)
/fastfs/rschoene/linux-git/drivers/cpufreq/cpufreq_governor.c:168

        mod_delayed_work_on(cpu, system_wq, &cdbs->work, delay);
 2c8:   48 8b 35 00 00 00 00    mov    0x0(%rip),%rsi        # 2cf <gov_queue_work+0x6f>
                        2cb: R_X86_64_PC32      system_wq-0x4
 2cf:   48 8d 50 30             lea    0x30(%rax),%rdx
 2d3:   4c 89 f9                mov    %r15,%rcx
 2d6:   89 df                   mov    %ebx,%edi
 2d8:   e8 00 00 00 00          callq  2dd <gov_queue_work+0x7d>
                        2d9: R_X86_64_PC32      mod_delayed_work_on-0x4
cpumask_next():
/fastfs/rschoene/linux-git/include/linux/cpumask.h:182 (discriminator 1)
 2dd:   41 83 c4 01             add    $0x1,%r12d
 2e1:   be 00 01 00 00          mov    $0x100,%esi
 2e6:   4c 89 ef                mov    %r13,%rdi
 2e9:   49 63 d4                movslq %r12d,%rdx
 2ec:   e8 00 00 00 00          callq  2f1 <gov_queue_work+0x91>
                        2ed: R_X86_64_PC32      find_next_bit-0x4



> If you are using x86 then simply use objdump, otherwise your toolchain will
> have a command for this..
> 
> Then search for gov_queue_work in this and confirm the length of routine is
> 0xd0 (Came from gov_queue_work+0x68/0xd0) and then tell us what's there
> at 0x68 ...
> 
> Sorry if you already knew all this, just for completeness I am sharing this :)
> 
> If you find some difficulty with this, just attach the file and send it to me +
> let me know what compiler you used, + system architecture.



  reply	other threads:[~2014-10-10 14:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  7:04 [PATCH 1/2] cpufreq: serialize calls to __cpufreq_governor() Viresh Kumar
2014-10-08 12:46 ` Prarit Bhargava
2014-10-10  9:04   ` Viresh Kumar
2014-10-10 10:41     ` Robert Schöne
2014-10-10 11:14       ` Viresh Kumar
2014-10-10 11:21     ` Prarit Bhargava
2014-10-10 11:30       ` Viresh Kumar
2014-10-10 11:38         ` Prarit Bhargava
2014-10-10 11:46           ` Viresh Kumar
2014-10-10 11:48             ` Prarit Bhargava
2014-10-10 12:01               ` Robert Schöne
2014-10-10 12:39                 ` Viresh Kumar
2014-10-10 13:04                   ` Robert Schöne
2014-10-10 13:23                   ` Robert Schöne
2014-10-10 13:52                     ` Viresh Kumar
2014-10-10 14:05                       ` Robert Schöne [this message]
2014-10-14  6:58                         ` Viresh Kumar
2014-10-14 11:42                           ` Prarit Bhargava
2014-10-14 17:12                             ` Prarit Bhargava
2014-10-16 10:58                               ` Viresh Kumar
2014-10-17 12:12                                 ` Prarit Bhargava
2014-10-16 10:57                             ` Viresh Kumar
2014-10-17 12:09                               ` Prarit Bhargava
  -- strict thread matches above, loose matches on Subject: below --
2014-10-10 13:55 Prarit Bhargava
2014-10-10 13:58 ` Viresh Kumar
2014-10-10 13:40 Prarit Bhargava
2014-10-10 13:42 ` Robert Schöne
2014-09-09  4:16 Viresh Kumar
2014-09-09  7:29 ` Robert Schöne
2014-09-09  7:35   ` Viresh Kumar
     [not found]   ` <540EEA95.8030208@redhat.com>
2014-09-09 14:45     ` Viresh Kumar
2014-09-24 23:46 ` Rafael J. Wysocki
2014-09-25  6:07   ` Robert Schöne
2014-09-29  9:50   ` Viresh Kumar
2014-09-29 11:29 ` Prarit Bhargava
2014-09-29 11:38   ` Viresh Kumar
2014-09-29 11:50     ` Prarit Bhargava
2014-09-29 11:55       ` Viresh Kumar

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=1412949926.13463.47.camel@x200t \
    --to=robert.schoene@tu-dresden.de \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=skannan@codeaurora.org \
    --cc=viresh.kumar@linaro.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