From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>,
kvm@vger.kernel.org, Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>,
Igor Mammedov <imammedo@redhat.com>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH 1/5] KVM: Make the maximum number of user memslots a per-VM thing
Date: Mon, 08 Feb 2021 15:20:03 +0100 [thread overview]
Message-ID: <87a6seod4c.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <538aec50-b448-fbd8-7c65-2f5a50d3874d@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 28/01/21 18:31, Sean Christopherson wrote:
>>
>>> For now I applied patches 1-2-5.
>> Why keep patch 1? Simply raising the limit in patch 2 shouldn't require per-VM
>> tracking.
>
> Well, right you are.
>
... so are we going to raise it after all? I don't see anything in
kvm/queue so just wanted to double-check.
Thanks!
--
Vitaly
next prev parent reply other threads:[~2021-02-08 14:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 17:57 [PATCH 0/5] KVM: Make the maximum number of user memslots configurable and raise the default Vitaly Kuznetsov
2021-01-27 17:57 ` [PATCH 1/5] KVM: Make the maximum number of user memslots a per-VM thing Vitaly Kuznetsov
2021-01-27 22:27 ` Maciej S. Szmigiero
2021-01-28 8:45 ` Vitaly Kuznetsov
2021-01-28 10:48 ` Maciej S. Szmigiero
2021-01-28 13:01 ` Paolo Bonzini
2021-01-28 15:26 ` Vitaly Kuznetsov
2021-01-28 17:31 ` Sean Christopherson
2021-01-28 17:59 ` Paolo Bonzini
2021-02-08 14:20 ` Vitaly Kuznetsov [this message]
2021-02-08 15:02 ` Paolo Bonzini
2021-01-27 17:57 ` [PATCH 2/5] KVM: Raise the maximum number of user memslots Vitaly Kuznetsov
2021-01-27 17:57 ` [PATCH 3/5] KVM: Make the maximum number of user memslots configurable Vitaly Kuznetsov
2021-01-27 17:57 ` [PATCH 4/5] selftests: kvm: Test the newly introduced KVM_CAP_MEMSLOTS_LIMIT Vitaly Kuznetsov
2021-01-27 17:57 ` [PATCH 5/5] selftests: kvm: Raise the default timeout to 120 seconds Vitaly Kuznetsov
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=87a6seod4c.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=imammedo@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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