Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1036065

Summary:	IRQBALANCE_BANNED_CPUS doesn't work
Product:	Red Hat Enterprise Linux 6	Reporter:	James Hogarth <james.hogarth>
Component:	irqbalance	Assignee:	Petr Holasek <pholasek>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.5	CC:	dhoward, dsulliva, jeder
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-23 13:40:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Hogarth 2013-11-29 10:32:52 UTC

Description of problem:
The issue is that in activate.c, applied_mask variable gets set to the cpu mask of the "local_cpus" value of the device. This ignores anything in banned_cpus.

So, made the change in the attached patch, which basically just does a cpus_andnot and makes sure that the resulting mask isn't 0.

Version-Release number of selected component (if applicable):
1.0.4-4

How reproducible:
Always

Steps to Reproduce:
1. Follow steps upstream


Actual results:
Specific CPU's won't be banned in a NUMA setup

Expected results:
Specific CPU's be banned in a NUMA setup

Additional info:
https://code.google.com/p/irqbalance/issues/detail?id=43
Fixed upstream in 1.0.6 git commit 1d8948271e2e81a7155ebe6c1b0abbead75416a