Hello! > I wonder how it works for you. Do you aware of an alternative way to > configure the clock > irqflags for more then 24 cores, or is it just ignored.
Unfortunately i don't know how it works. > My current status is as follows: > With 64 cores there is no printouts what so ever. > With 32 cores the boot usually get stuck after the message "[ 45.719102] > SCSI subsystem > initialized" > With 24 cores the system noontimes complete the boot and sometimes get stuck > like the 32 > cores system. I will recheck later when i get back to qemu. I will pull the latest HEAD and fix IRQ affinity specification. But, i think that most likely you'll have to debug this yourself. Because i suggest it will work. :) >> Yes, i just left it as it was because it already works fine with ARM64. >> Actually, >> TYPE_AARCH64_CPU is a subclass of TYPE_ARM_CPU. > > I see but I guess that I want aarch64_cpu_initfn to be called and not > arm_cpu_initfn. I guess that the correct class will be returned. Otherwise it would not work at all. You can check this if you want to. >> BTW, just for interest, have you tried to do anything with KVM support of >> vGICv3? I have >> some code but it's inherently unstable and lock up for unknown (yet) reason. > > No, this is because I don't have an ARM64 based server needed for running KVM > for ARM64. Ok. Then it looks like i'm going to be the first to do this. I hope you'll complete the integration soon because vGICv3 has to be based upon your work. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia
