similar to: [PATCH v4] s390/virtio: add BSD license to virtio-ccw

On Tue, 28 Nov 2017 15:17:52 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > The original intent of the virtio header relicensing > from 2008 was to make sure anyone can implement compatible > devices/drivers. The virtio-ccw was omitted by mistake. > > We have an ack from the only contributor as well as the > maintainer from IBM, so it's not too late

2017-10-20 14:59 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: > On Thu, Oct 19, 2017 at 09:11:00PM +0300, Matwey V. Kornilov wrote: >> >> Hello, >> >> I use libvirt 3.3.0 and qemu 2.9.0 >> >> My domain XML spec is the following: >> >> <domain type='qemu'> >> <name>s390_generic</name> >>

Hello, I use libvirt 3.3.0 and qemu 2.9.0 My domain XML spec is the following: <domain type='qemu'> <name>s390_generic</name> <uuid>82b4d16e-b636-447e-9fda-41d44616bce8</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu

The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22: virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20181219 for you to fetch changes up to 6fb95ef30707f1b2fcaea8d6dc873055e0460b1a: virtio-ccw: diag 500 may return a negative cookie

The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22: virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20181219 for you to fetch changes up to 6fb95ef30707f1b2fcaea8d6dc873055e0460b1a: virtio-ccw: diag 500 may return a negative cookie

Hi all, In another series I proposed to add an architecture specific callback to fail feature negociation on architecture need. In VIRTIO, we already have an entry to reject the features on the transport basis. Transport is not architecture so I send a separate series in which we fail the feature negociation inside virtio_ccw_finalize_features, the virtio_config_ops.finalize_features for S390

Hi all, In another series I proposed to add an architecture specific callback to fail feature negociation on architecture need. In VIRTIO, we already have an entry to reject the features on the transport basis. Transport is not architecture so I send a separate series in which we fail the feature negociation inside virtio_ccw_finalize_features, the virtio_config_ops.finalize_features for S390

The file arch/s390/include/uapi/asm/virtio-ccw.h belongs to the s390 virtio drivers as well. Signed-off-by: Cornelia Huck <cohuck at redhat.com> --- Martin, Heiko: It's probably best to take this through your tree. --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6671f375f7fc..48c6f1179b9b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS

The file arch/s390/include/uapi/asm/virtio-ccw.h belongs to the s390 virtio drivers as well. Signed-off-by: Cornelia Huck <cohuck at redhat.com> --- Martin, Heiko: It's probably best to take this through your tree. --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 6671f375f7fc..48c6f1179b9b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS

The following changes since commit 8c0f9f5b309d627182d5da72a69246f58bde1026: Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name" (2018-09-25 13:28:58 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/virtio-ccw-20180926 for you to fetch changes up to

Hi, here's the guest driver support for adapter interrupts in virtio-ccw. We use one summary indicator per page of indicators. For each device, we try to find a space in an indicator where all of its virtqueues fit. Locking probably needs some more love, but it seems to work fine so far. Cornelia Huck (2): KVM: s390: virtio-ccw: Handle command rejects. KVM: s390: virtio-ccw adapter

Hi, here's the guest driver support for adapter interrupts in virtio-ccw. We use one summary indicator per page of indicators. For each device, we try to find a space in an indicator where all of its virtqueues fit. Locking probably needs some more love, but it seems to work fine so far. Cornelia Huck (2): KVM: s390: virtio-ccw: Handle command rejects. KVM: s390: virtio-ccw adapter

Hi, next version of the guest exploitation of virtio-ccw adapter interrupts. Changes from the last version: - adapt to latest kvm-next - changed housekeeping for indicator locations: we now use cacheline-sized and aligned areas - minor tweaks Cornelia Huck (2): KVM: s390: virtio-ccw: Handle command rejects. KVM: s390: virtio-ccw adapter interrupt support. arch/s390/include/asm/irq.h

Hi, next version of the guest exploitation of virtio-ccw adapter interrupts. Changes from the last version: - adapt to latest kvm-next - changed housekeeping for indicator locations: we now use cacheline-sized and aligned areas - minor tweaks Cornelia Huck (2): KVM: s390: virtio-ccw: Handle command rejects. KVM: s390: virtio-ccw adapter interrupt support. arch/s390/include/asm/irq.h

On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote: > On Wed, 19 Dec 2018 11:14:13 +0100 > Cornelia Huck <cohuck at redhat.com> wrote: > > > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22: > > > > virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500) > > > > are available in the Git repository at: >

On Thu, Jan 03, 2019 at 09:55:07AM +0100, Cornelia Huck wrote: > On Wed, 19 Dec 2018 11:14:13 +0100 > Cornelia Huck <cohuck at redhat.com> wrote: > > > The following changes since commit 37d1246af2d530710cf5822d2845774f01c03b22: > > > > virtio_net: bulk free tx skbs (2018-12-06 14:28:39 -0500) > > > > are available in the Git repository at: >

If something goes wrong in the kvm io bus handling, the virtio-ccw diagnose may return a negative error value in the cookie gpr. Document this. Signed-off-by: Cornelia Huck <cohuck at redhat.com> --- Even if the virtio spec is the correct place to specify what diag 500 subcode 3 does, we also should mention here that the cookie may be an error. ---

On Thu, 29 Nov 2018 15:56:48 +0100 Cornelia Huck <cohuck at redhat.com> wrote: > On Wed, 26 Sep 2018 18:48:28 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > The following changes since commit 8c0f9f5b309d627182d5da72a69246f58bde1026: > > > > Revert "uapi/linux/keyctl.h: don't use C++ reserved keyword as a struct member name"

These patches implement the new read status command in qemu and bump the revision to 2 (as this ccw is currently the only thing new with that revision). Patches are on top of v2 of "virtio-1/virtio-ccw related patches". Pierre Morel (2): s390x/virtio-ccw: respond to READ_STATUS command s390x/virtio-ccw: set revision 2 as maximum revision number hw/s390x/virtio-ccw.c | 20

These patches implement the new read status command in qemu and bump the revision to 2 (as this ccw is currently the only thing new with that revision). Patches are on top of v2 of "virtio-1/virtio-ccw related patches". Pierre Morel (2): s390x/virtio-ccw: respond to READ_STATUS command s390x/virtio-ccw: set revision 2 as maximum revision number hw/s390x/virtio-ccw.c | 20