Re: Availability of physical devices and migration (was: Re: [RFC PATCH 2/2] vfio-ccw: Connect the device request notifier)

2020-11-20 Thread Halil Pasic
On Fri, 20 Nov 2020 12:38:37 +0100 Cornelia Huck wrote: > On Fri, 20 Nov 2020 03:51:07 +0100 > Halil Pasic wrote: > > > On Tue, 17 Nov 2020 04:26:05 +0100 > > Eric Farman wrote: > > > > > Now that the vfio-ccw code has a notifier interface to request tha

Re: [PATCH 4/4] docs: documentation for virtio packed option

2020-03-27 Thread Halil Pasic
On Thu, 26 Mar 2020 11:32:14 +0100 Bjoern Walk wrote: > + > + The attribute packed controls the usage of packed > + virtqueues. This reads to me, like if packed='on' is specified, then packed virtqueues are used (or the device fails); if packed='off' is specified is specified

Re: [libvirt] [PATCH RFC 1/1] allow to specify additional config data

2019-06-13 Thread Halil Pasic
On Thu, 6 Jun 2019 16:44:17 +0200 Cornelia Huck wrote: > Add a rough implementation for vfio-ap. > > Signed-off-by: Cornelia Huck > --- > mdevctl.libexec | 25 ++ > mdevctl.sbin| 56 - > 2 files changed, 80

Re: [libvirt] mdevctl: A shoestring mediated device management and persistence utility

2019-06-12 Thread Halil Pasic
On Wed, 12 Jun 2019 09:14:39 +0200 Cornelia Huck wrote: > On Tue, 11 Jun 2019 14:28:22 -0600 > Alex Williamson wrote: > > > On Tue, 11 Jun 2019 21:45:08 +0200 > > Cornelia Huck wrote: > > > > > On Fri, 7 Jun 2019 18:06:30 +0200 > > > Halil Pasi

Re: [libvirt] mdevctl: A shoestring mediated device management and persistence utility

2019-06-12 Thread Halil Pasic
On Tue, 11 Jun 2019 21:45:08 +0200 Cornelia Huck wrote: > On Fri, 7 Jun 2019 18:06:30 +0200 > Halil Pasic wrote: > > > On Fri, 24 May 2019 12:11:06 +0200 > > Cornelia Huck wrote: > > > > > On Thu, 23 May 2019 17:20:01 -0600 > > >

Re: [libvirt] mdevctl: A shoestring mediated device management and persistence utility

2019-06-07 Thread Halil Pasic
On Fri, 24 May 2019 12:11:06 +0200 Cornelia Huck wrote: > On Thu, 23 May 2019 17:20:01 -0600 > Alex Williamson wrote: > > > Hi, > > [..] > > > > It would be really useful if s390 folks could help me understand > > whether it's possible to glean all the information necessary to > > recreate

Re: [libvirt] [Qemu-devel] [PATCH for-3.1] s390x: remove 's390-squash-mcss' option

2018-07-30 Thread Halil Pasic
On 07/24/2018 11:24 AM, Cornelia Huck wrote: This option has been deprecated for two releases; remove it. Signed-off-by: Cornelia Huck Acked-by: Halil Pasic --- hw/s390x/3270-ccw.c| 2 +- hw/s390x/css-bridge.c | 1 - hw/s390x/css.c

Re: [libvirt] Question about using cpu mode "host-model" while providing a cpu model name

2018-05-09 Thread Halil Pasic
On 05/09/2018 12:41 PM, Jiri Denemark wrote: On Tue, May 08, 2018 at 10:44:22 -0400, Collin Walling wrote: Hi I have noticed something that may be misconstrued regarding the libvirt domain xml format for defining a cpu model. There seems to be a misalignment where the libvirt documentation

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-27 Thread Halil Pasic
On 10/27/2017 07:12 PM, Jiri Denemark wrote: > On Fri, Oct 27, 2017 at 17:18:44 +0200, Halil Pasic wrote: >> On 10/27/2017 04:06 PM, Christian Borntraeger wrote: > ... >>> I talked to several people and it seems that on x86 the host model will >>> also enable new f

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-27 Thread Halil Pasic
On 10/27/2017 04:06 PM, Christian Borntraeger wrote: > > > On 10/27/2017 03:40 PM, Halil Pasic wrote: >> >> >> On 10/27/2017 02:57 PM, Christian Borntraeger wrote: >>> >>> >>> On 10/27/2017 02:45 PM, Christian Borntraeger wrote: >>>

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-27 Thread Halil Pasic
On 10/27/2017 03:31 PM, Cornelia Huck wrote: > On Fri, 27 Oct 2017 14:42:57 +0200 > Christian Borntraeger wrote: > >> Yes, we should also replace that with >> >> return s390_has_feat(S390_FEAT_GUARDED_STORAGE) >> >> I can fixup my patch or provide a 2nd one. >> > >

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-27 Thread Halil Pasic
On 10/27/2017 02:57 PM, Christian Borntraeger wrote: > > > On 10/27/2017 02:45 PM, Christian Borntraeger wrote: >> >> >> On 10/27/2017 02:31 PM, Halil Pasic wrote: >> gs is explicitly disabled. >>> >>> Now that I think about it, maybe the 2.9

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-27 Thread Halil Pasic
On 10/25/2017 08:13 PM, Jason J. Herne wrote: > On 10/20/2017 10:54 AM, Christian Borntraeger wrote: >> Starting a guest with >>     >> hvm >>    >>    >> >> on an IBM z14 results in >> >> "qemu-system-s390x: Some features requested in the CPU model are not >> available in the

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-26 Thread Halil Pasic
On 10/26/2017 10:13 AM, Christian Borntraeger wrote: > > > On 10/26/2017 01:35 AM, Halil Pasic wrote: > try the most interesting scenarios out. >> >> The idea of the patch is very clear, but I don't understand the bigger gs >> feature context fully. >

Re: [libvirt] [Qemu-devel] [PATCH/QEMU] s390x/kvm: use cpu_model_available for guarded storage on compat machines

2017-10-25 Thread Halil Pasic
ed to give a timely review, so I've limited myself there. >From what I see, this patch does what it advertises, and since I think it's the right thing to do in the current situation I gonna give it an: Acked-by: Halil Pasic <pa...@linux.vnet.ibm.com> At the same time, I would prefer the commit mes

Re: [libvirt] [Qemu-devel] Question about the host-model CPU mode

2017-10-20 Thread Halil Pasic
On 10/20/2017 04:12 PM, Christian Borntraeger wrote: > > > On 10/20/2017 04:06 PM, David Hildenbrand wrote: >> On 20.10.2017 16:02, Christian Borntraeger wrote: >>> >>> >>> On 10/20/2017 03:51 PM, David Hildenbrand wrote: >>> [...] > The problem goes much further. > A fresh guest with