Bug 458276 - Need mechanism to catch IRQ thread creation and re-run rtctl
Need mechanism to catch IRQ thread creation and re-run rtctl
Status: CLOSED DUPLICATE of bug 466929
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-utilities (Show other bugs)
1.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jon Masters
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-07 09:32 EDT by Clark Williams
Modified: 2008-11-20 16:29 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-20 16:29:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Clark Williams 2008-08-07 09:32:43 EDT
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 16:29:23 EST
same topic

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

Note You need to log in before you can comment on or make changes to this bug.