Re: [PATCH v1 07/14] s390x/s390-hypercall: introduce DIAG500 STORAGE_LIMIT

[Janosch Frank]

On 9/12/24 10:19 AM, Thomas Huth wrote:
> On 10/09/2024 19.58, David Hildenbrand wrote:

[...]

> > diff --git a/hw/s390x/s390-hypercall.h b/hw/s390x/s390-hypercall.h
> > index b7ac29f444..f0ca62bcbb 100644
> > --- a/hw/s390x/s390-hypercall.h
> > +++ b/hw/s390x/s390-hypercall.h
> > @@ -18,6 +18,7 @@
> >    #define DIAG500_VIRTIO_RESET            1 /* legacy */
> >    #define DIAG500_VIRTIO_SET_STATUS       2 /* legacy */
> >    #define DIAG500_VIRTIO_CCW_NOTIFY       3 /* KVM_S390_VIRTIO_CCW_NOTIFY */
> > +#define DIAG500_STORAGE_LIMIT           4
> >    
> >    int handle_diag_500(CPUS390XState *env);
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
> Sounds very reasonable to me - but it would be good to get an
> Ack/Reviewed-by from IBM folks here (in case they prefer a different
> interface)... hope they'll join the discussion!

I've publicized the series on the internal channels yesterday.
We're aware of the fact that we need to provide review.