From: Stefan Hajnoczi <stefanha@gmail.com>
To: Nir Levy <nirl@asocsnetworks.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Yan Fridland <yan@asocsnetworks.com>
Subject: Re: [Qemu-devel] QEMU-guestOS latencies.
Date: Mon, 8 Aug 2016 16:10:41 +0100 [thread overview]
Message-ID: <20160808151041.GC25553@stefanha-x1.localdomain> (raw)
In-Reply-To: <AM4PR06MB16010DD6EF0FD7624ADC7ECACC000@AM4PR06MB1601.eurprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
On Thu, Jul 28, 2016 at 09:25:41AM +0000, Nir Levy wrote:
> in addition I wish to understand ram allocation and avoid host swaps.
I didn't read everything but this stood out. QEMU has a -realtime
mlock=on option if you wish to mlock(2) guest memory on the host.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-08-08 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 9:25 [Qemu-devel] QEMU-guestOS latencies Nir Levy
2016-08-08 15:10 ` Stefan Hajnoczi [this message]
2016-08-09 11:45 ` Nir Levy
2016-08-11 9:10 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2016-07-28 16:37 Nir Levy
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=20160808151041.GC25553@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=nirl@asocsnetworks.com \
--cc=qemu-devel@nongnu.org \
--cc=yan@asocsnetworks.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).