Bug 458276

Summary:	Need mechanism to catch IRQ thread creation and re-run rtctl
Product:	Red Hat Enterprise MRG	Reporter:	Clark Williams <williams>
Component:	realtime-utilities	Assignee:	Jon Masters <jcm>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1	CC:	bhu, williams
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-20 21:29:23 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:

Description Clark Williams 2008-08-07 13:32:43 UTC

Description of problem:
IRQ threads in the RT kernel are created when a driver registers an interrupt and are killed when the interrupt is unregistered. This means that if a module is reloaded, a new IRQ thread will be created, with it's default priority, as opposed to the desired priority specified in /etc/rtgroups. 

We need a mechanism to catch IRQ thread creation and re-run rtcl to adjust thread priorities.

Comment 1 Clark Williams 2008-11-20 21:29:23 UTC

same topic

*** This bug has been marked as a duplicate of bug 466929 ***