Hotpatching will be ugly because we need both versions - for eg:
xen_intr_register_xname() aliases to intr_register_xname() in DomU and Dom0 but
we need both in the case of PVHVM.
So the other option is function pointers - but this will require re-prototyping
all function names that PVHVM touc
On December 28, 2018 9:54:11 PM GMT+05:30, John Nemeth
wrote:
>On Dec 28, 7:36pm, "Cherry G.Mathew" wrote:
>} Maxime Villard writes:
>} > Le 28/12/2018 �� 14:57, Cherry G.Mathew a ��crit :
>} >> Maxime Villard writes:
>} Introduce a weak alias method of exporting different
>implementation
On December 28, 2018 11:28:01 PM GMT+05:30, Jason Thorpe wrote:
>
>> On Dec 28, 2018, at 9:50 AM, Mathew, Cherry G. wrote:
>>
>> That seems like a dependency burden on people developing new
>features. I can't tell if modload is the only way to get NVMM to run.
>
On December 28, 2018 9:54:11 PM GMT+05:30, John Nemeth
wrote:
>On Dec 28, 7:36pm, "Cherry G.Mathew" wrote:
>} Maxime Villard writes:
>} > Le 28/12/2018 �� 14:57, Cherry G.Mathew a ��crit :
>} >> Maxime Villard writes:
>} Introduce a weak alias method of exporting different
>implementation
On December 28, 2018 8:40:11 PM GMT+05:30, Jason Thorpe wrote:
>
>> On Dec 28, 2018, at 6:06 AM, Cherry G.Mathew wrote:
>>
>> I don't like the imperative in your tone. NVMM is the user of
>modloader,
>> not PVHVM. So if you feel like your usecase needs fixing, I'd say
>it's
>> your problem - or
On December 28, 2018 7:58:10 PM GMT+05:30, Maxime Villard
wrote:
>Le 28/12/2018 à 15:06, Cherry G.Mathew a écrit :
>> Maxime Villard writes:
>>> Le 28/12/2018 à 14:57, Cherry G.Mathew a écrit :
Maxime Villard writes:
>> Introduce a weak alias method of exporting different
>implementati
