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

CONFIG_IRQ_REMAP in default kernel configuration #6264

Closed
marcinfalkiewicz opened this issue Feb 9, 2015 · 4 comments
Closed

CONFIG_IRQ_REMAP in default kernel configuration #6264

marcinfalkiewicz opened this issue Feb 9, 2015 · 4 comments
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 6.topic: kernel The Linux kernel

Comments

@marcinfalkiewicz
Copy link
Contributor

Is there any particular reason why interrupt remapping isn't enabled by default?

There is workaround by using allow_unsafe_interrupts=1 option of vfio_iommu_type1, but it's not ideal and can lead to crash of the host or escalate their privileges on the host (VM's on NixOS are running as root user; it can be changed in qemu.conf).
@domenkozar domenkozar added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Feb 17, 2015
@domenkozar
Copy link
Member

cc @edolstra

@edolstra
Copy link
Member

@iElectric I don't really know what this does, but it seems fine to enable it...

@thoughtpolice thoughtpolice added the 6.topic: kernel The Linux kernel label Jun 1, 2015
@Profpatsch
Copy link
Member

(triage) updates?

@joachifm
Copy link
Contributor

joachifm commented May 5, 2017

I believe this can be closed:

$ grep IRQ_REMAP $(nix-build -A linux.configfile)
CONFIG_IRQ_REMAP=y

@joachifm joachifm closed this as completed May 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.severity: security Issues which raise a security issue, or PRs that fix one 6.topic: kernel The Linux kernel
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@thoughtpolice @joachifm @domenkozar @edolstra @marcinfalkiewicz @Profpatsch