Re: [PATCH] hw/acpi: Remove legacy reset handling from vmclock

2025-04-08 Thread Ani Sinha
> On Apr 9, 2025, at 09:53, Ani Sinha wrote: > > > >> On Feb 7, 2025, at 20:04, David Woodhouse wrote: >> >> From: David Woodhouse >> >> The vmclock device only has a reset method in order to plug its memory >> region into the system memory. It was originally done this way in order >> to

Re: [PATCH] hw/acpi: Remove legacy reset handling from vmclock

2025-04-08 Thread Ani Sinha
> On Feb 7, 2025, at 20:04, David Woodhouse wrote: > > From: David Woodhouse > > The vmclock device only has a reset method in order to plug its memory > region into the system memory. It was originally done this way in order > to defer the memory_region_add_subregion_overlap() from vmclock_

Re: [PATCH] hw/acpi: Remove legacy reset handling from vmclock

2025-04-05 Thread Ani Sinha
On Sat, Mar 29, 2025 at 1:43 PM David Woodhouse wrote: > > On Fri, 2025-02-07 at 14:34 +, David Woodhouse wrote: > > From: David Woodhouse > > > > The vmclock device only has a reset method in order to plug its memory > > region into the system memory. It was originally done this way in order

Re: [PATCH] hw/acpi: Remove legacy reset handling from vmclock

2025-03-29 Thread David Woodhouse
On Fri, 2025-02-07 at 14:34 +, David Woodhouse wrote: > From: David Woodhouse > > The vmclock device only has a reset method in order to plug its memory > region into the system memory. It was originally done this way in order > to defer the memory_region_add_subregion_overlap() from vmclock_