On 07/04/2017 06:59 PM, Cornelia Huck wrote:
> On Tue, 4 Jul 2017 17:08:52 +0200
> Halil Pasic wrote:
>
> cd.type = KVM_DEV_TYPE_FLIC;
> ret = kvm_vm_ioctl(kvm_state, KVM_CREATE_DEVICE, );
> if (ret < 0) {
> -
On Tue, 4 Jul 2017 17:08:52 +0200
Halil Pasic wrote:
> >>> cd.type = KVM_DEV_TYPE_FLIC;
> >>> ret = kvm_vm_ioctl(kvm_state, KVM_CREATE_DEVICE, );
> >>> if (ret < 0) {
> >>> -trace_flic_create_device(errno);
> >>> -return;
> >>> +
On 07/04/2017 04:46 PM, Halil Pasic wrote:
>
>
> On 07/04/2017 04:31 PM, Cornelia Huck wrote:
>> On Tue, 4 Jul 2017 16:07:55 +0200
>> Christian Borntraeger wrote:
>>
>>> From: Halil Pasic
>>>
>>> From the moment it was introduced by commit
On 07/04/2017 04:31 PM, Cornelia Huck wrote:
> On Tue, 4 Jul 2017 16:07:55 +0200
> Christian Borntraeger wrote:
>
>> From: Halil Pasic
>>
>> From the moment it was introduced by commit a2875e6f98 ("s390x/kvm:
>> implement floating-interrupt
On Tue, 4 Jul 2017 16:07:55 +0200
Christian Borntraeger wrote:
> From: Halil Pasic
>
> From the moment it was introduced by commit a2875e6f98 ("s390x/kvm:
> implement floating-interrupt controller device", 2013-07-16) the kvm-flic
> is not
From: Halil Pasic
>From the moment it was introduced by commit a2875e6f98 ("s390x/kvm:
implement floating-interrupt controller device", 2013-07-16) the kvm-flic
is not making realize fail properly in case it's impossible to create the
KVM device which basically serves