From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] kvm: rename HINTS_DEDICATED to KVM_HINTS_REALTIME
Date: Fri, 18 May 2018 11:41:23 +0200 [thread overview]
Message-ID: <a95b2a12-f3a9-b930-49fe-46c2278df34d@redhat.com> (raw)
In-Reply-To: <20180517184658.GA1543@localhost.localdomain>
On 17/05/2018 20:46, Eduardo Habkost wrote:
> My understanding of the original patch is that the intention is
> to tell the guest that it is very unlikely to be preempted, so it
> can choose a more appropriate spinlock implementation. This
> description implies that the guest will never be preempted, which
> is much stronger guarantee.
>
> Isn't this new description incompatible with existing usage of
> the hint, which might include people who just use vCPU pinning
> but no mlock?
If you use hugetlbfs and vhost-user you don't really need mlock for the
QEMU process, do you? The QEMU process is not doing much in that case
and hugetlbfs gives you pinned memory automatically.
Paolo
next prev parent reply other threads:[~2018-05-18 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 14:54 Michael S. Tsirkin
2018-05-17 16:05 ` Paolo Bonzini
2018-05-17 18:46 ` Eduardo Habkost
2018-05-17 19:55 ` Michael S. Tsirkin
2018-05-18 16:04 ` Eduardo Habkost
2018-05-18 17:01 ` Michael S. Tsirkin
2018-05-18 17:13 ` Eduardo Habkost
2018-05-18 17:18 ` Paolo Bonzini
2018-05-18 17:54 ` Eduardo Habkost
2018-05-18 17:17 ` Paolo Bonzini
2018-05-18 9:41 ` Paolo Bonzini [this message]
2018-05-18 12:47 ` Michael S. Tsirkin
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=a95b2a12-f3a9-b930-49fe-46c2278df34d@redhat.com \
--to=pbonzini@redhat.com \
--cc=corbet@lwn.net \
--cc=ehabkost@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®