similar to: Reading parts of data files

On 26/04/2019 20:32, Halil Pasic wrote: > This will come in handy soon when we pull out the indicators from > virtio_ccw_device to a memory area that is shared with the hypervisor > (in particular for protected virtualization guests). > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 40

On 26/04/2019 20:32, Halil Pasic wrote: > This will come in handy soon when we pull out the indicators from > virtio_ccw_device to a memory area that is shared with the hypervisor > (in particular for protected virtualization guests). > > Signed-off-by: Halil Pasic <pasic at linux.ibm.com> > --- > drivers/s390/virtio/virtio_ccw.c | 40

On 08/05/2019 16:31, Pierre Morel wrote: > On 26/04/2019 20:32, Halil Pasic wrote: >> This will come in handy soon when we pull out the indicators from >> virtio_ccw_device to a memory area that is shared with the hypervisor >> (in particular for protected virtualization guests). >> >> Signed-off-by: Halil Pasic <pasic at linux.ibm.com> >> --- >>

On 09/05/2019 20:26, Halil Pasic wrote: > On Thu, 9 May 2019 14:01:01 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 08/05/2019 16:31, Pierre Morel wrote: >>> On 26/04/2019 20:32, Halil Pasic wrote: >>>> This will come in handy soon when we pull out the indicators from >>>> virtio_ccw_device to a memory area that is shared with

On 09/05/2019 20:26, Halil Pasic wrote: > On Thu, 9 May 2019 14:01:01 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 08/05/2019 16:31, Pierre Morel wrote: >>> On 26/04/2019 20:32, Halil Pasic wrote: >>>> This will come in handy soon when we pull out the indicators from >>>> virtio_ccw_device to a memory area that is shared with

On 10/05/2019 13:54, Halil Pasic wrote: > On Fri, 10 May 2019 09:43:08 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 09/05/2019 20:26, Halil Pasic wrote: >>> On Thu, 9 May 2019 14:01:01 +0200 >>> Pierre Morel <pmorel at linux.ibm.com> wrote: >>> >>>> On 08/05/2019 16:31, Pierre Morel wrote: >>>>> On

On 10/05/2019 13:54, Halil Pasic wrote: > On Fri, 10 May 2019 09:43:08 +0200 > Pierre Morel <pmorel at linux.ibm.com> wrote: > >> On 09/05/2019 20:26, Halil Pasic wrote: >>> On Thu, 9 May 2019 14:01:01 +0200 >>> Pierre Morel <pmorel at linux.ibm.com> wrote: >>> >>>> On 08/05/2019 16:31, Pierre Morel wrote: >>>>> On

I have an array with 44800 columns and 24 rows I would like to compute the row average for the array 100 columns at a time, so I would like to end up with an array of 24 rows x 448 columns. I have tried using apply(dataset, 1, function(x) mean(x[])), but I am not sure how to get it to take the average 100 columns at a time. Any ideas would be welcomed. thanks, Spencer [[alternative HTML

Dear all, I have a question about how to get a matrix by combining a large number of columns from a data file. Suppose I read a file which have 1000 columns by: test = read.table("dat.txt", header=F) I know I could use "cbind()". It's easy to do when the number of columns is small (i.e. cbind(test$V1, test$V2)). But how about build a matrix "X" by combine the

On 26/04/2019 20:32, Halil Pasic wrote: > Before virtio-ccw could get away with not using DMA API for the pieces of > memory it does ccw I/O with. With protected virtualization this has to > change, since the hypervisor needs to read and sometimes also write these > pieces of memory. > > The hypervisor is supposed to poke the classic notifiers, if these are > used, out of

On 26/04/2019 20:32, Halil Pasic wrote: > Before virtio-ccw could get away with not using DMA API for the pieces of > memory it does ccw I/O with. With protected virtualization this has to > change, since the hypervisor needs to read and sometimes also write these > pieces of memory. > > The hypervisor is supposed to poke the classic notifiers, if these are > used, out of

Hi Michael, here are two virtio/s390 patches (one cleanup, one bugfix), prepared against your vhost branch of mst/vhost.git. Please apply. Cornelia Huck (1): virtio/s390: size of SET_IND payload Geliang Tang (1): virtio/s390: use dev_to_virtio drivers/s390/virtio/virtio_ccw.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) -- 2.3.9

Hi Michael, here are two virtio/s390 patches (one cleanup, one bugfix), prepared against your vhost branch of mst/vhost.git. Please apply. Cornelia Huck (1): virtio/s390: size of SET_IND payload Geliang Tang (1): virtio/s390: use dev_to_virtio drivers/s390/virtio/virtio_ccw.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) -- 2.3.9

This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> --- drivers/s390/virtio/virtio_ccw.c | 40 +++++++++++++++++++++++++--------------- 1 file changed, 25 insertions(+), 15 deletions(-) diff --git

From: Halil Pasic <pasic at linux.ibm.com> This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> --- drivers/s390/virtio/virtio_ccw.c | 40

This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> Reviewed-by: Cornelia Huck <cohuck at redhat.com> --- drivers/s390/virtio/virtio_ccw.c

From: Halil Pasic <pasic at linux.ibm.com> This will come in handy soon when we pull out the indicators from virtio_ccw_device to a memory area that is shared with the hypervisor (in particular for protected virtualization guests). Signed-off-by: Halil Pasic <pasic at linux.ibm.com> Reviewed-by: Pierre Morel <pmorel at linux.ibm.com> Signed-off-by: Michael Mueller <mimu at

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV

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