From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Michael Mueller <mimu@linux.ibm.com>, frankja@linux.vnet.ibm.com
Cc: kvm@vger.kernel.org, cohuck@redhat.com, david@redhat.com,
thuth@redhat.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: introduce module parameter kvm.use_gisa
Date: Thu, 27 Feb 2020 17:23:18 +0100 [thread overview]
Message-ID: <2ec3f6d2-105d-62bc-774a-bb4d71ed5c93@de.ibm.com> (raw)
In-Reply-To: <20200227091031.102993-1-mimu@linux.ibm.com>
On 27.02.20 10:10, Michael Mueller wrote:
> The boolean module parameter "kvm.use_gisa" controls if newly
> created guests will use the GISA facility if provided by the
> host system. The default is yes.
>
> # cat /sys/module/kvm/parameters/use_gisa
> Y
>
> The parameter can be changed on the fly.
>
> # echo N > /sys/module/kvm/parameters/use_gisa
>
> Already running guests are not affected by this change.
>
> The kvm s390 debug feature shows if a guest is running with GISA.
>
> # grep gisa /sys/kernel/debug/s390dbf/kvm-$pid/sprintf
> 00 01582725059:843303 3 - 08 00000000e119bc01 gisa 0x00000000c9ac2642 initialized
> 00 01582725059:903840 3 - 11 000000004391ee22 00[0000000000000000-0000000000000000]: AIV gisa format-1 enabled for cpu 000
> ...
> 00 01582725059:916847 3 - 08 0000000094fff572 gisa 0x00000000c9ac2642 cleared
>
> In general, that value should not be changed as the GISA facility
> enhances interruption delivery performance.
>
> A reason to switch the GISA facility off might be a performance
> comparison run or debugging.
>
> Signed-off-by: Michael Mueller <mimu@linux.ibm.com>
Thanks applied.
prev parent reply other threads:[~2020-02-27 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 9:10 [PATCH] KVM: s390: introduce module parameter kvm.use_gisa Michael Mueller
2020-02-27 9:26 ` David Hildenbrand
2020-02-27 12:04 ` Michael Mueller
2020-02-27 12:31 ` David Hildenbrand
2020-02-27 12:57 ` Michael Mueller
2020-02-27 9:47 ` Cornelia Huck
2020-02-27 12:19 ` Michael Mueller
2020-02-27 12:27 ` Christian Borntraeger
2020-02-27 12:43 ` Michael Mueller
2020-02-27 13:24 ` Christian Borntraeger
2020-02-27 16:10 ` Michael Mueller
2020-02-27 12:48 ` Cornelia Huck
2020-02-27 12:56 ` Michael Mueller
2020-02-27 16:23 ` Christian Borntraeger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ec3f6d2-105d-62bc-774a-bb4d71ed5c93@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mimu@linux.ibm.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox