Radim,
Thanks for your answer. Indeed setting IRQ affinity to a specific core
seems to be respected.
However, on software emulation and on the real machine, while IRQ
affinity defaults to 3, all interrupts go on CPU0, while on KVM they go
on CPU1.
I wonder why KVM would act differently
On 21/08/2015 05:33, Mihai Neagu wrote:
Radim,
Thanks for your answer. Indeed setting IRQ affinity to a specific core
seems to be respected.
However, on software emulation and on the real machine, while IRQ
affinity defaults to 3, all interrupts go on CPU0, while on KVM they go
on
2015-08-20 17:16+0300, Mihai Neagu:
Here is how IRQ affinity is configured on guest at startup, in an init.d
script:
echo 1 /proc/irq/default_smp_affinity
for x in /proc/irq/*/smp_affinity;
do
echo 1 $x
done 2 /dev/null
The command line for starting the hardware accelerated VM:
Hello,
I'm trying to assign some IRQ affinities to core 0 by setting
smp_affinity to 1.
This is on a dual-core embedded Linux virtual machine ran with KVM.
However, ISRs continue to run on both cores.
The same technique works well with QEMU with full software emulation.
Here is the output of
