> On 05/04/2019 14:24, Hajkowski wrote: > > From: Marcin Hajkowski <[email protected]> > > > > Use new guest channel API to send confirmation message for received > > power command. > > > > Signed-off-by: Marcin Hajkowski <[email protected]> > > --- > > examples/vm_power_manager/channel_monitor.c | 68 > +++++++++++++++++++-- > > 1 file changed, 62 insertions(+), 6 deletions(-) > > > > diff --git a/examples/vm_power_manager/channel_monitor.c > > b/examples/vm_power_manager/channel_monitor.c > > index 7892d75de..ed580b36a 100644 > > --- a/examples/vm_power_manager/channel_monitor.c > > +++ b/examples/vm_power_manager/channel_monitor.c
<...> > > Using the guest_cli sample app in a VM, sending commands to the > vm_power_manager app on the host, we now have Acks and Nacks coming > from the host to the VM to conform the execution of the guest requests. > > vmpower(guest)> set_cpu_freq 3 down > ACK received for message sent to host. > vmpower(guest)> set_cpu_freq 3 up > ACK received for message sent to host. > vmpower(guest)> set_cpu_freq 3 up > NACK received for message sent to host. > > (NACK because we're already at the maxumum frequency) > > And in the host vm_power_manager command line, we can see when a > guest request cannot be processed: > POWER: Turbo is off, frequency can't be scaled up more 31 > > Patchset looks good functionally. > > Tested-by: David Hunt <[email protected]> Acked-by: Lee Daly <[email protected]>
