From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, pkrempa@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt
Date: Thu, 26 Feb 2015 13:54:33 -0700 [thread overview]
Message-ID: <54EF8809.8060601@redhat.com> (raw)
In-Reply-To: <1424980156-25556-3-git-send-email-lcapitulino@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
On 02/26/2015 12:49 PM, Luiz Capitulino wrote:
> This document describes how to use memory hotplug in QEMU.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> docs/memory-hotplug.txt | 77 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 77 insertions(+)
> create mode 100644 docs/memory-hotplug.txt
>
> diff --git a/docs/memory-hotplug.txt b/docs/memory-hotplug.txt
> new file mode 100644
> index 0000000..e821449
> --- /dev/null
> +++ b/docs/memory-hotplug.txt
> @@ -0,0 +1,77 @@
> +QEMU memory hotplug
> +===================
> +
Might be worth adding a copyright and license notice.
> +
> +Creates a guest with 1GB of memory and three hotpluggable memory slots.
> +The hotpluggable memory slots are empty when the guest is booted, so all
> +memory the guest will see after boot is 1GB. The maximum memory the
> +guest can reach is 4GB. This means that three additional gigas can be
s/gigas/gigabytes/
> +
> +For example, assuming that the host has 1GB hugepages available in
> +the /mnt/hugepages-1GB directory, a 1GB hugepage could be hotplugged
> +into the guest from the previous section with the following commnands:
s/commnands/commands/
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-02-26 20:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 19:49 [Qemu-devel] [PATCH 0/2] improve memory hotplug documentation Luiz Capitulino
2015-02-26 19:49 ` [Qemu-devel] [PATCH 1/2] qemu-options.hx: improve -m description Luiz Capitulino
2015-03-02 14:50 ` Peter Krempa
2015-03-02 15:03 ` Igor Mammedov
2015-02-26 19:49 ` [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt Luiz Capitulino
2015-02-26 20:54 ` Eric Blake [this message]
2015-03-02 9:59 ` Paulo Ricardo Paz Vital
2015-03-02 21:51 ` Luiz Capitulino
2015-03-02 14:52 ` Peter Krempa
2015-03-02 15:06 ` Igor Mammedov
-- strict thread matches above, loose matches on Subject: below --
2015-03-02 22:14 [Qemu-devel] [PATCH v2 0/2] improve memory hotplug documentation Luiz Capitulino
2015-03-02 22:14 ` [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt Luiz Capitulino
2015-03-03 13:20 ` Igor Mammedov
2015-03-03 14:32 ` Luiz Capitulino
2015-03-03 17:40 ` Eric Blake
2015-03-03 17:57 ` Luiz Capitulino
2015-03-03 14:47 [Qemu-devel] [PATCH v3 0/2] improve memory hotplug documentation Luiz Capitulino
2015-03-03 14:47 ` [Qemu-devel] [PATCH 2/2] docs: add memory-hotplug.txt Luiz Capitulino
2015-03-03 15:12 ` Paulo Ricardo Paz Vital
2015-03-03 16:16 ` Luiz Capitulino
2015-03-04 8:16 ` Paulo Ricardo Paz Vital
2015-03-04 15:50 ` Luiz Capitulino
2015-03-04 12:04 ` Igor Mammedov
2015-03-04 17:00 ` Paulo Ricardo Paz Vital
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=54EF8809.8060601@redhat.com \
--to=eblake@redhat.com \
--cc=imammedo@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).