From: Pengyu Ma <pengyu.ma@windriver.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
<rafael.j.wysocki@intel.com>, <linux-kernel@vger.kernel.org>,
"Box, David E" <david.e.box@intel.com>,
"Anvin, H Peter" <h.peter.anvin@intel.com>
Subject: Re: [PATCH] powercap / RAPL : remove dependency on iosf_mbi
Date: Sat, 26 Sep 2015 11:42:56 +0800 [thread overview]
Message-ID: <56061440.1060007@windriver.com> (raw)
In-Reply-To: <20150924093341.744c26d4@icelake>
$ objdump --dwarf drivers/powercap/intel_rapl.o |grep iosf
<65ad> DW_AT_name : (indirect string, offset: 0x3644):
iosf_mbi_read
<65f7> DW_AT_name : (indirect string, offset: 0x496):
iosf_mbi_write
5 3 0 0 iosf_mbi.h
0x00000490 656c5f69 6400696f 73665f6d 62695f77 el_id.iosf_mbi_w
0x00003640 72656700 696f7366 5f6d6269 5f726561 reg.iosf_mbi_rea
$ grep -i iosf_mbi .config
# CONFIG_IOSF_MBI is not set
It is compiled and included by header file.
Pengyu
On 09/25/2015 12:33 AM, Jacob Pan wrote:
> On Thu, 24 Sep 2015 18:03:32 +0800
> Pengyu Ma <pengyu.ma@windriver.com> wrote:
>
>>> So the problematic case is when RAPL=Y IOSF=M
>>> Since real IOSF functions are available when
>>> #if IS_ENABLED(CONFIG_IOSF_MBI)
>>> There will be no dummy functions for RAPL to reference in this
>>> case.
>> iosf_mbi_write/read will warn itself.
> it does not compile.
next prev parent reply other threads:[~2015-09-26 3:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 7:31 [PATCH] powercap / RAPL : remove dependency on iosf_mbi Pengyu Ma
2015-09-18 0:09 ` Rafael J. Wysocki
2015-09-18 15:43 ` Jacob Pan
2015-09-21 3:48 ` Pengyu Ma
2015-09-21 21:36 ` Jacob Pan
2015-09-22 3:11 ` Pengyu Ma
2015-09-22 17:01 ` Jacob Pan
2015-09-24 10:03 ` Pengyu Ma
2015-09-24 15:09 ` Austin S Hemmelgarn
2015-09-24 16:33 ` Jacob Pan
2015-09-26 3:42 ` Pengyu Ma [this message]
2015-09-28 16:13 ` Jacob Pan
2015-09-22 13:41 ` Austin S Hemmelgarn
2015-09-22 15:57 ` Jacob Pan
2015-09-22 17:00 ` Austin S Hemmelgarn
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=56061440.1060007@windriver.com \
--to=pengyu.ma@windriver.com \
--cc=david.e.box@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/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.