From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: paulus@samba.org, sjitindarsingh@gmail.com, agraf@suse.de,
mdroth@linux.vnet.ibm.com, thuth@redhat.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv3 2/5] pseries: Stubs for HPT resizing
Date: Wed, 14 Dec 2016 17:12:01 +1100 [thread overview]
Message-ID: <20161214061201.GH32647@umbus> (raw)
In-Reply-To: <4431c63f-7ecc-d38b-df05-a428c0b98a63@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
On Tue, Dec 13, 2016 at 03:29:05PM +0100, Laurent Vivier wrote:
>
>
> On 12/12/2016 05:06, David Gibson wrote:
> > This introduces stub implementations of the H_RESIZE_HPT_PREPARE and
> > H_RESIZE_HPT_COMMIT hypercalls which we hope to add in a PAPR
> > extension to allow run time resizing of a guest's hash page table. It
> > also adds a new machine property for controlling whether this new
> > facility is available, and logic to check that against availability
> > with KVM (only supported with KVM PR for now).
> >
> > Finally, it adds a new string to the hypertas property in the device
> > tree, advertising to the guest the availability of the HPT resizing
> > hypercalls. This is a tentative suggested value, and would need to be
> > standardized by PAPR before being merged.
>
> Could you explain somewhere what is the aim of the "flags" parameter?
> It could help to understand why we have it as it is not used.
It's mostly just there on the general principle that have some way of
extending is a good idea.
As an example of a possible extension, we could have a flag which
caused all the valid HPTEs to be rehashed, instead of just the bolted
ones - we'd need to do tests to see if that was worthwhile (probably a
tradeoff between commit downtime and post-resize performance).
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-14 21:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 4:05 [Qemu-devel] [PATCHv3 0/5] Hash Page Table resizing for TCG pseries guests David Gibson
2016-12-12 4:05 ` [Qemu-devel] [PATCHv3 1/5] pseries: Add pseries-2.9 machine type David Gibson
2016-12-12 4:06 ` [Qemu-devel] [PATCHv3 2/5] pseries: Stubs for HPT resizing David Gibson
2016-12-13 14:29 ` Laurent Vivier
2016-12-14 6:12 ` David Gibson [this message]
2016-12-14 5:22 ` Suraj Jitindar Singh
2016-12-15 1:07 ` David Gibson
2016-12-12 4:06 ` [Qemu-devel] [PATCHv3 3/5] pseries: Implement " David Gibson
2016-12-14 5:30 ` Suraj Jitindar Singh
2016-12-14 6:20 ` David Gibson
2016-12-14 23:20 ` Suraj Jitindar Singh
2016-12-15 0:59 ` David Gibson
2016-12-14 5:35 ` Suraj Jitindar Singh
2016-12-15 1:03 ` David Gibson
2016-12-12 4:06 ` [Qemu-devel] [PATCHv3 4/5] pseries: Enable HPT resizing for 2.9 David Gibson
2016-12-14 5:32 ` Suraj Jitindar Singh
2016-12-14 6:20 ` David Gibson
2016-12-14 23:08 ` Suraj Jitindar Singh
2016-12-12 4:06 ` [Qemu-devel] [PATCHv3 5/5] pseries: Use smaller default hash page tables when guest can resize David Gibson
2016-12-14 5:56 ` Suraj Jitindar Singh
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=20161214061201.GH32647@umbus \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sjitindarsingh@gmail.com \
--cc=thuth@redhat.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).