[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio-dev] Re: [PATCH 1/4] content: Introduce driver/device auxiliary notifications
On Thu, 11 Aug 2022 10:53:35 +0200 Cornelia Huck <cohuck@redhat.com> wrote: > On Wed, Aug 10 2022, Halil Pasic <pasic@linux.ibm.com> wrote: > > > On Wed, 10 Aug 2022 11:54:35 +0200 > > Cornelia Huck <cohuck@redhat.com> wrote: > > > >> >> These device-specific notifications are needed later when adding support > >> >> for virtio-vhost-user device. > >> >> > >> >> Signed-off-by: Usama Arif <usama.arif@bytedance.com> > >> >> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> > >> >> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com> > >> > > >> > I see ccw is missing. Cornelia, any suggestions? > >> > >> Hmm... I seem to be really behind on ccw things :( > >> > >> We can probably use the following: > >> > >> - for device->driver notification, use the next bit in the secondary > >> indicators (bit 0 is used for config change notification) > >> - for driver->device notification, maybe use a new subcode for diagnose > >> 0x500 (4 is probably the next free one?) > >> > > > > Sounds reasonable! I will have to double check the DIAG stuff though. I'm > > not sure where what needs to be reserved and documented. > > There's > https://gitlab.com/davidhildenbrand/s390x-os-virt-spec/-/merge_requests/1, > but nothing much has happened there recently. David? Hm, that seems to be private. I land on a sign-in page. Regards, Halil
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]