public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: intel_rapl: No such device
Date: Mon, 28 Apr 2014 03:51:57 -0700	[thread overview]
Message-ID: <20140428035157.6e9458e6@jacob-desktop> (raw)
In-Reply-To: <201404261224.45353@pali>

On Sat, 26 Apr 2014 12:24:45 +0200
Pali Rohár <pali.rohar@gmail.com> wrote:

> Hello,
> 
> on intel haswell mobile cpu it is not possible to load intel_rapl 
> driver. Modprobe will show this error message:
> 
> intel_rapl.ko': -1 No such device
> intel_rapl: driver does not support CPU family 6 model 60
> 
> Is not intel mobile cpu supported by intel_rapl?
> 
> 
intel_rapl should support this model. I just haven't got a chance to
test on this particular part.
I will send out a patch soon and CC you.

Thanks,

Jacob
> Here is info from /proc/cpuinfo
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 60
> model name      : Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz
> stepping        : 3
> microcode       : 0x17
> cpu MHz         : 2585.375
> cache size      : 3072 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 2
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep 
> mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss 
> ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon 
> pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu 
> pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma 
> cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat 
> epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid 
> fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm
> bogomips        : 5187.99
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 39 bits physical, 48 bits virtual
> power management:
> 
> 
> And from /sys/devices/system/cpu/modalias
> 
> cpu:type:x86,ven0000fam0006mod003C:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000E,000F,0010,0011,0013,0015,0016,0017,0018,0019,001A,001B,001C,001D,001F,002B,0034,003A,003B,003D,0068,006B,006C,006D,006F,0070,0072,0074,0075,0076,0078,007C,007D,0080,0081,0082,0083,0084,0085,0086,0087,0088,0089,008B,008C,008D,008E,008F,0091,0093,0094,0095,0096,0097,0098,0099,009A,009B,009C,009D,009E,00C0,00C5,00E0,00E1,00E3,00E4,00E5,00E6,00E7,0100,0101,0102,0103,0104,0120,0121,0123,0124,0125,0127,0128,0129,012A,012B,012D
> 

[Jacob Pan]

  reply	other threads:[~2014-04-28 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26 10:24 intel_rapl: No such device Pali Rohár
2014-04-28 10:51 ` Jacob Pan [this message]
2014-05-06 20:14   ` Pali Rohár

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=20140428035157.6e9458e6@jacob-desktop \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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