[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH/RFC] KVM: s390: Add S390 configuration and contr
From: |
Christian Borntraeger |
Subject: |
Re: [Qemu-devel] [PATCH/RFC] KVM: s390: Add S390 configuration and control kvm device |
Date: |
Tue, 01 Apr 2014 17:04:51 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
On 01/04/14 16:58, Alexander Graf wrote:
> On 04/01/2014 04:47 PM, Christian Borntraeger wrote:
>> From: Ekaterina Tumanova <address@hidden>
>>
>> Add KVM_DEV_TYPE_S390_CONFIG kvm device that contains
>> configuration and control attributes of particular vm.
>> The device is created by KVM_CREATE_DEVICE ioctl.
>> The attributes may be retrieved and stored by calling
>> KVM_GET_DEVICE_ATTR and KVM_SET_DEVICE_ATTR ioctls.
>>
>> Signed-off-by: Ekaterina Tumanova <address@hidden>
>> Signed-off-by: Christian Borntraeger <address@hidden>
>
> I don't think a device is particularly the best fit. A device can usually be
> instantiated multiple times. The configuration device can only be created
> once. A device also gets created by user space which enables it to receive
> the fd to drive it. Your device has to be created during VM creation.
I remember some discussion a year or 2 ago, and IIRC a config device
was actually your idea ;-) (The other idea that we had, was ONE_REG for the VM)
>
> I think VM configuration is common enough to just make this a separate
> interface.
So you propose to define a new base ioctl (e.g. VM_REG) on the vm fd, instead?
Seems like an easy enough change. Would you reuse the kvm_attr structure for
that?
>
>
> Alex
>
Re: [Qemu-devel] [PATCH/RFC] s390: Provide a configuration and control device, Alexander Graf, 2014/04/01
Re: [Qemu-devel] [PATCH/RFC] s390: Provide a configuration and control device, Christian Borntraeger, 2014/04/02