Bug 596694

Summary:	PMQoS dbus (/proc) communication problem
Product:	Red Hat Enterprise Linux 6	Reporter:	Jan Ščotka <jscotka>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	agospoda, azelinka, notting, rhughes, snagar
Target Milestone:	rc	Keywords:	Regression, RHELNAK
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-05 05:35:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	519967
Bug Blocks:

Description Jan Ščotka 2010-05-27 10:24:22 UTC

There was a problem with kernel interface for PMQoS some times ago.
How is state now? It is okay now.
There should be communication over Dbus between
power management - dbus - kernel - proc dirs

Comment 2 Richard Hughes 2010-06-01 12:37:11 UTC

The /dev/cpu_dma_latency and /dev/network_latency device files are missing in el6 and fedora kernels for some reason.

The supported devices are the e1000e, ipw2100, and igbvf. I have the former installed, so I should be getting the pmqos interface files. I'm doing some more debugging now, and am waiting for test kernels to compile.

Comment 3 Andy Gospodarek 2010-06-04 15:28:57 UTC

Seems to be working for me:

$ uname -a 
Linux eeepc 2.6.32.9-70.fc12.i686 #1 SMP Wed Mar 3 05:14:32 UTC 2010 i686 i686 i386 GNU/Linux
$ ls /dev | grep latency
cpu_dma_latency
network_latency

Comment 4 Richard Hughes 2010-06-21 13:46:03 UTC

I'm half way through a test document. I should be finished in the next few days.

Comment 6 RHEL Program Management 2010-07-28 16:37:43 UTC

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **