[XEN PATCH v2 04/15] x86/p2m: move altp2m-related code to separate file

2024-05-15 Thread Sergiy Kibrik
Move altp2m code from generic p2m.c file to altp2m.c, so it is kept separately and can possibly be disabled in the build. We may want to disable it when building for specific platform only, that doesn't support alternate p2m. No functional change intended. Signed-off-by: Sergiy Kibrik CC: Tamas

Re: [XEN PATCH v2 04/15] x86/p2m: move altp2m-related code to separate file

2024-05-15 Thread Stefano Stabellini
On Wed, 15 May 2024, Sergiy Kibrik wrote: > Move altp2m code from generic p2m.c file to altp2m.c, so it is kept separately > and can possibly be disabled in the build. We may want to disable it when > building for specific platform only, that doesn't support alternate p2m. > > No functional change

Re: [XEN PATCH v2 04/15] x86/p2m: move altp2m-related code to separate file

2024-05-16 Thread Jan Beulich
On 15.05.2024 11:06, Sergiy Kibrik wrote: > --- a/xen/arch/x86/mm/p2m.c > +++ b/xen/arch/x86/mm/p2m.c > @@ -500,7 +500,7 @@ int p2m_alloc_table(struct p2m_domain *p2m) > return 0; > } > > -static int __must_check > +int __must_check > p2m_remove_entry(struct p2m_domain *p2m, gfn_t gfn, mfn

Re: [XEN PATCH v2 04/15] x86/p2m: move altp2m-related code to separate file

2024-05-16 Thread Jan Beulich
On 16.05.2024 02:35, Stefano Stabellini wrote: > On Wed, 15 May 2024, Sergiy Kibrik wrote: >> Move altp2m code from generic p2m.c file to altp2m.c, so it is kept >> separately >> and can possibly be disabled in the build. We may want to disable it when >> building for specific platform only, that