Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

activate_mapping: report explicit errors on failure #266

Closed
wants to merge 2 commits into from
Closed

activate_mapping: report explicit errors on failure #266

wants to merge 2 commits into from

Commits on Jul 5, 2023

  1. activate_mapping: report explicit errors on failure 

    Make sure to report the exact reason why the affinity cannot be
enforced. No need to call fflush() since it is called internally in
fclose().

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2184735
Signed-off-by: Robin Jarry <rjarry@redhat.com>
    @rjarry
    rjarry committed Jul 5, 2023
    Configuration menu
    Copy the full SHA
    621d19d View commit details
    Browse the repository at this point in the history

  2. activate_mapping: do not ban irq on out of space error 

    If smp_affinity cannot be enforced on a given IRQ because the kernel
returns an ENOSPC error, do not ban it for the rest of the process'
life.

Only log the warning and let irqbalance try again later.

If the kernel returns any other error (like EIO when trying to change
affinity for PPI interrupts on aarch64), add it to ban list.

Fixes: 55c5c32 ("arm64: Add irq aff change check For aarch64 ...")
Signed-off-by: Robin Jarry <rjarry@redhat.com>
    @rjarry
    rjarry committed Jul 5, 2023
    Configuration menu
    Copy the full SHA
    18ae4e2 View commit details
    Browse the repository at this point in the history