qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH/RFC] s390: Provide a configuration and control d


From: Alexander Graf
Subject: Re: [Qemu-devel] [PATCH/RFC] s390: Provide a configuration and control device
Date: Tue, 01 Apr 2014 16:59:35 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130910 Thunderbird/17.0.9

On 04/01/2014 04:47 PM, Christian Borntraeger wrote:
We want to configure several things in KVM that go beyond what
ENABLE_CAP (we need payload) or ONE_REG (we need it for the VM
and we need to do more complex actions) can provide. Instead of
adding several s390 specific ioctls, lets provide a configuration
and control device that encapsulates different commands into
groups of the same area (MEMORY, CPU, ..)

We also provide an initial nameless base group, with a simple first
user to set the guest name. We need that name in the kernel for
the emulation of STSI (which provides the guest name to the guest)
but we need to implement the emulation in supervisor mode, as it
also provides the underlying levels of hipervisors.

Currently we have the following GROUPS and ATTRs pending, which
configure some memory management related function or allow to set
the guest facilities, cpuids etc:

#define KVM_DEV_CONFIG_GROUP            0
#define KVM_DEV_CONFIG_NAME             0

#define KVM_DEV_CONFIG_GROUP_MEM        1
#define KVM_DEV_CONFIG_MEM_ENABLE_CMMA  0
#define KVM_DEV_CONFIG_MEM_CLR_CMMA     1
#define KVM_DEV_CONFIG_MEM_CLR_PAGES    2

#define KVM_DEV_CONFIG_GROUP_CPU        2
#define KVM_DEV_CONFIG_CPU_TYPE         0
#define KVM_DEV_CONFIG_CPU_FAC          1
#define KVM_DEV_CONFIG_CPU_FAC_MASK     2
#define KVM_DEV_CONFIG_CPU_IBC          3
#define KVM_DEV_CONFIG_CPU_IBC_RANGE    4

Why would CPU specific information be set in the VM?


Alex




In addition other groups like
#define KVM_DEV_CONFIG_GROUP_CRYPTO
are under consideration to configure crypto acceleration.

Unless there is a major concern, I will add this to the next
s390 PULL requests for KVM.

Christian





reply via email to

[Prev in Thread] Current Thread [Next in Thread]