From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>,
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
Sean Christopherson <seanjc@google.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Igor Mammedov <imammedo@redhat.com>,
Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Huacai Chen <chenhuacai@kernel.org>,
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
Paul Mackerras <paulus@ozlabs.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] KVM: Scalable memslots implementation
Date: Wed, 3 Feb 2021 14:46:41 +0100 [thread overview]
Message-ID: <307603f3-52a8-7464-ba98-06cbe4ddd408@redhat.com> (raw)
In-Reply-To: <5efd931f-9d69-2936-89e8-278fe106616d@redhat.com>
On 03/02/21 14:44, David Hildenbrand wrote:
> BTW: what are your thoughts regarding converting the rmap array on
> x86-64 into some dynamic datastructre (xarray etc)? Has that already
> been discussed?
Hasn't been discussed---as always, showing the code would be the best
way to start a discussion. :)
However, note that the TDP MMU does not need an rmap at all. Since that
one is getting ready to become the default, the benefits of working on
the rmap would be quite small and only affect nested virtualization.
Paolo
next prev parent reply other threads:[~2021-02-03 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 8:13 [PATCH 1/2] KVM: x86/mmu: Make HVA handler retpoline-friendly Maciej S. Szmigiero
2021-02-01 8:13 ` [PATCH 2/2] KVM: Scalable memslots implementation Maciej S. Szmigiero
2021-02-02 1:33 ` Sean Christopherson
2021-02-02 22:42 ` Maciej S. Szmigiero
2021-02-02 23:43 ` Sean Christopherson
2021-02-03 10:44 ` Maciej S. Szmigiero
2021-02-03 14:21 ` Vitaly Kuznetsov
2021-02-03 20:10 ` Maciej S. Szmigiero
2021-02-03 13:43 ` Paolo Bonzini
2021-02-03 13:41 ` Paolo Bonzini
2021-02-03 13:44 ` David Hildenbrand
2021-02-03 13:46 ` Paolo Bonzini [this message]
2021-02-03 13:52 ` David Hildenbrand
2021-02-03 14:33 ` Paolo Bonzini
2021-02-03 20:09 ` Maciej S. Szmigiero
2021-02-01 8:21 ` [PATCH 1/2] KVM: x86/mmu: Make HVA handler retpoline-friendly Paolo Bonzini
2021-02-01 15:19 ` Maciej S. Szmigiero
2021-02-03 14:43 ` Paolo Bonzini
2021-02-03 20:09 ` Maciej S. Szmigiero
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=307603f3-52a8-7464-ba98-06cbe4ddd408@redhat.com \
--to=pbonzini@redhat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=chenhuacai@kernel.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imammedo@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=james.morse@arm.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=maz@kernel.org \
--cc=paulus@ozlabs.org \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).