From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>
Cc: KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [PATCH] KVM: s390: remove delayed reallocation of page tables for KVM
Date: Thu, 23 Apr 2015 14:07:07 +0200 [thread overview]
Message-ID: <5538E06B.8090507@redhat.com> (raw)
In-Reply-To: <5538DAD4.4060505@de.ibm.com>
On 23/04/2015 13:43, Christian Borntraeger wrote:
>> >
>> > Couldn't you make this a hidden kconfig option that gets automatically selected when kvm is enabled? Or is there a non-kvm case that needs it too?
> For things like RHEV the default could certainly be "enabled", but for normal
> distros like SLES/RHEL, the idea was to NOT enable that by default, as the non-KVM
> case is more common and might suffer from the additional memory consumption of
> the page tables. (big databases come to mind)
>
> We could think about having rpms like kvm to provide a sysctl file that sets it if we
> want to minimize the impact. Other ideas?
I can say what _won't_ work which is tying it to the KVM module.
Nowadays it is loaded automatically via udev on the first /dev/kvm
access, and that's already too late because qemu-kvm's page tables have
been created already. Right?
With my Fedora hat on, adding a sysctl file to the userspace RPMs (e.g.
qemu) would work. CCing Cole Robinson who is the main maintainer of the
Fedora virt packages.
Paolo
next prev parent reply other threads:[~2015-04-23 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 11:08 [PATCH] page table bugfix for s390/kvm Christian Borntraeger
2015-04-23 11:08 ` [PATCH] KVM: s390: remove delayed reallocation of page tables for KVM Christian Borntraeger
2015-04-23 11:37 ` Alexander Graf
2015-04-23 11:43 ` Christian Borntraeger
2015-04-23 12:01 ` Alexander Graf
2015-04-23 12:08 ` Christian Borntraeger
2015-04-27 13:49 ` Alexander Graf
2015-04-23 12:13 ` Martin Schwidefsky
2015-04-27 13:48 ` Alexander Graf
2015-04-27 13:52 ` Paolo Bonzini
2015-04-27 13:57 ` Martin Schwidefsky
2015-04-27 14:03 ` Alexander Graf
2015-04-27 14:08 ` Christian Borntraeger
2015-04-23 12:07 ` Paolo Bonzini [this message]
2015-04-23 13:57 ` Cole Robinson
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=5538E06B.8090507@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=crobinso@redhat.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.