Re: [PATCH v2 1/5] x86/HVM: introduce hvm_point_entry()

2023-11-22 Thread Andrew Cooper
On 22/11/2023 9:34 am, Jan Beulich wrote: > On 21.11.2023 22:30, Andrew Cooper wrote: >> On 16/11/2023 1:46 pm, Jan Beulich wrote: >>> ... to accompany hvm_read_entry() when actual copying isn't desirable. >>> This allows to remove open-coded stream accesses from hpet_load(), >>> along with using t

Re: [PATCH v2 1/5] x86/HVM: introduce hvm_point_entry()

2023-11-22 Thread Jan Beulich
On 21.11.2023 22:30, Andrew Cooper wrote: > On 16/11/2023 1:46 pm, Jan Beulich wrote: >> ... to accompany hvm_read_entry() when actual copying isn't desirable. >> This allows to remove open-coded stream accesses from hpet_load(), >> along with using the helper in hvm_load() itself. >> >> Since arch

Re: [PATCH v2 1/5] x86/HVM: introduce hvm_point_entry()

2023-11-21 Thread Andrew Cooper
On 16/11/2023 1:46 pm, Jan Beulich wrote: > ... to accompany hvm_read_entry() when actual copying isn't desirable. > This allows to remove open-coded stream accesses from hpet_load(), > along with using the helper in hvm_load() itself. > > Since arch_hvm_load()'s declaration would need changing, an

[PATCH v2 1/5] x86/HVM: introduce hvm_point_entry()

2023-11-16 Thread Jan Beulich
... to accompany hvm_read_entry() when actual copying isn't desirable. This allows to remove open-coded stream accesses from hpet_load(), along with using the helper in hvm_load() itself. Since arch_hvm_load()'s declaration would need changing, and since the function is not used from elsewhere, pu