On 05/01/2026 9:17 pm, Jason Andryuk wrote:
> On 2026-01-05 14:57, Andrew Cooper wrote:
>> The most recent xenoprof change was 300ef0cb4fde ("x86: Add Xenoprofile
>> support for AMD Family16h") in 2013, despite there being 42 changes
>> worth of
>> other cleanup/rearranging since then.
>>
>> Oprofile themselves dropped Xen support in commit 0c142c3a096d ("Remove
>> opcontrol and the GUI and processor models dependent on it") in 2014,
>> as part
>> of releasing version 1.0 and switching over to using operf based on
>> the Linux
>> perf_event subsystem. Linux's version of this patch was merged in
>> commit
>> 24880bef417f ("Merge tag 'oprofile-removal-5.12'") in 2021.
>>
>> Drop xenoprof and all supporting infrastructure, including the
>> hypercall, the
>> XSM hook and flask vectors which lose their only caller, and even
>> shrinks
>> struct domain by one pointer which wasn't properly excluded in
>> !CONFIG_XENOPROF builds.
>>
>> Retain the public xenoprof.h header as it is ABI, but note that the
>> functionality is removed.
>>
>> Signed-off-by: Andrew Cooper <[email protected]>
>
> Reviewed-by: Jason Andryuk <[email protected]>
Thanks.
>
> VPMU_PASSIVE_DOMAIN_ALLOCATED could be dropped as well - maybe in a
> follow up to re-number the remaining VPMU_ flags?
Oh - so it can. I'll fold in the deletion, but I'll leave the
renumbering for later.
~Andrew
