Avi Kivity wrote:
On 06/18/2009 03:09 PM, Gregory Haskins wrote:
We need to raise this limit drastically and to expose it.Yeah, its already naturally limited by the maximum number of MMIO/PIO+config KVM_MAX_IOSIGNALFD_ITEMSIs there a per-vm limit on iosignalfds? if not, userspace can exhaust
+ int "Maximum IOSIGNALFD items per address"
+ depends on KVM
+ default "32"
+ ---help---
+ This option influences the maximum number of fd's per PIO/MMIO
+ address that are allowed to register
+
kernel memory in that way.
devices we can register (today this is 6 per VM). I should have
documented that fact somewhere, tho.
Any suggestions on a target #? 512?
No, a u16 will naturally expand to a u64, and the emulator will
generate the correct value.
Right, I understand that part. What I mean specifically is at run-time
when the IO comes in. I was thinking I would need to do a memcmp
against the u64 and the data-register and it was hurting my head trying
to figure out what pointer to pass to memcmp.
<lightbulb turns on>
Duh, I can just load the data-register into a u64 and check equality.
Nevermind, I am a dumbass ;)