Re: [PATCH v2 3/3] x86: detect PIT aliasing on ports other than 0x4[0-3]

2024-05-14 Thread Jason Andryuk
On 2024-05-14 03:43, Jan Beulich wrote: On 10.05.2024 19:40, Jason Andryuk wrote: On 2023-12-18 09:48, Jan Beulich wrote: --- a/xen/arch/x86/time.c +++ b/xen/arch/x86/time.c @@ -425,6 +425,72 @@ static struct platform_timesource __init .resume = resume_pit, }; +unsigned int __init

Re: [PATCH v2 3/3] x86: detect PIT aliasing on ports other than 0x4[0-3]

2024-05-14 Thread Jan Beulich
On 10.05.2024 19:40, Jason Andryuk wrote: > On 2023-12-18 09:48, Jan Beulich wrote: >> --- a/xen/arch/x86/time.c >> +++ b/xen/arch/x86/time.c >> @@ -425,6 +425,72 @@ static struct platform_timesource __init >> .resume = resume_pit, >> }; >> >> +unsigned int __initdata pit_alias_mask; >>

Re: [PATCH v2 3/3] x86: detect PIT aliasing on ports other than 0x4[0-3]

2024-05-10 Thread Jason Andryuk
On 2023-12-18 09:48, Jan Beulich wrote: ... in order to also deny Dom0 access through the alias ports. Without this it is only giving the impression of denying access to PIT. Unlike for CMOS/RTC, do detection pretty early, to avoid disturbing normal operation later on (even if typically we won't

[PATCH v2 3/3] x86: detect PIT aliasing on ports other than 0x4[0-3]

2023-12-18 Thread Jan Beulich
... in order to also deny Dom0 access through the alias ports. Without this it is only giving the impression of denying access to PIT. Unlike for CMOS/RTC, do detection pretty early, to avoid disturbing normal operation later on (even if typically we won't use much of the PIT). Like for CMOS/RTC a