Skip to main content

Browse the archive

Revision 82c99f7a81f28f8c1be5f701c8377d14c4075b10 authored by Harry Pan on 24 April 2019, 14:50:33 UTC, committed by Ingo Molnar on 25 April 2019, 06:59:31 UTC 
perf/x86/intel: Update KBL Package C-state events to also include PC8/PC9/PC10 counters
 
Kaby Lake (and Coffee Lake) has PC8/PC9/PC10 residency counters.

This patch updates the list of Kaby/Coffee Lake PMU event counters
from the snb_cstates[] list of events to the hswult_cstates[]
list of events, which keeps all previously supported events and
also adds the PKG_C8, PKG_C9 and PKG_C10 residency counters.

This allows user space tools to profile them through the perf interface.

Signed-off-by: Harry Pan <harry.pan@intel.com>
Cc: <stable@vger.kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Vince Weaver <vincent.weaver@maine.edu>
Cc: gs0622@gmail.com
Link: http://lkml.kernel.org/r/20190424145033.1924-1-harry.pan@intel.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
1 parent cd8dead
Raw File
aty128fb.txt 
[This file is cloned from VesaFB/matroxfb]

What is aty128fb?
=================

This is a driver for a graphic framebuffer for ATI Rage128 based devices
on Intel and PPC boxes.

Advantages:

 * It provides a nice large console (128 cols + 48 lines with 1024x768)
   without using tiny, unreadable fonts.
 * You can run XF68_FBDev on top of /dev/fb0
 * Most important: boot logo :-)

Disadvantages:

 * graphic mode is slower than text mode... but you should not notice
   if you use same resolution as you used in textmode.
 * still experimental.


How to use it?
==============

Switching modes is done using the  video=aty128fb:<resolution>... modedb
boot parameter or using `fbset' program.

See Documentation/fb/modedb.txt for more information on modedb
resolutions.

You should compile in both vgacon (to boot if you remove your Rage128 from
box) and aty128fb (for graphics mode). You should not compile-in vesafb
unless you have primary display on non-Rage128 VBE2.0 device (see 
Documentation/fb/vesafb.txt for details).


X11
===

XF68_FBDev should generally work fine, but it is non-accelerated. As of
this document, 8 and 32bpp works fine.  There have been palette issues
when switching from X to console and back to X.  You will have to restart
X to fix this.


Configuration
=============

You can pass kernel command line options to vesafb with
`video=aty128fb:option1,option2:value2,option3' (multiple options should
be separated by comma, values are separated from options by `:'). 
Accepted options:

noaccel  - do not use acceleration engine. It is default.
accel    - use acceleration engine. Not finished.
vmode:x  - chooses PowerMacintosh video mode <x>. Deprecated.
cmode:x  - chooses PowerMacintosh colour mode <x>. Deprecated.
<XxX@X>  - selects startup videomode. See modedb.txt for detailed
	   explanation. Default is 640x480x8bpp.


Limitations
===========

There are known and unknown bugs, features and misfeatures.
Currently there are following known bugs:
 + This driver is still experimental and is not finished.  Too many
   bugs/errata to list here.

--
Brad Douglas <brad@neruo.com>
back to top