It is not needed to dynamic allocate idt vector. Instead,
reuse the vector of XENHVM since both cannot co-exist.
EVTCHN naming also apply to HYPERV since the interrupt is used to raise event as well.
Differential D5254
hyperv/vmbus: static assign IDT vector for hv howard0su_gmail.com on Feb 11 2016, 1:29 PM. Authored by Tags None Referenced Files
Subscribers
Details It is not needed to dynamic allocate idt vector. Instead, EVTCHN naming also apply to HYPERV since the interrupt is used to raise event as well.
Diff Detail
Event TimelineComment Actions How does this interact with D5291? AFAICT they are not compatible. In any case, IDT_EVTCHN should be renamed to IDT_HYPERVISOR. Comment Actions IMHO this IDT vector needs to be renamed to something that's not Xen-specific for HyperV to use it. Comment Actions We had a brainstorm last week, talked about the name. One funny thing is that in hyper-v, the interrupt vector is also used to service event, so we think EVTCHN seems fine :) Comment Actions I would suggest we use IDT_HYPERVISOR as Roger mentioned. Event Channel is a terminology in Xen's context. Comment Actions LGTM
Comment Actions amd64/machdep.c: #ifdef XENHVM I have considered a bit about how to handle this in a nice way. May be we need IDT_HYPERVISOR{1,2,3,4}? Define IDT_EVTCHAN as an alias to HYPERVISOR1, and IDT_HYPERV to HYPERVISOR2 etc. So this could be handled nicely. Else it would look pretty confusing at least to me, i.e. we override it later. |