Displaying 1 result from an estimated 1 matches for "shared_info_v2".
Did you mean:
shared_info_t
2010 May 21
10
increase evtchn limits
...box.
I overcame vcpu_info[MAX_VIRT_CPUS] by doing vcpu placement hypercall
in guest, but now running into evt channel limit (lots of devices):
unsigned long evtchn_pending[sizeof(unsigned long) * 8];
which limits to 512 max for my 64bit dom0. The only recourse seems to
create a new struct shared_info_v2{}, and re-arrange it a bit with lot
more event channels. Since, start_info has magic with version info, I
can just check that in guest and use new shared_info...(doing the design
on the fly here). I can create a new vcpuop saying the guest is using
newer version. Or forget new version of share...