qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: Alexander Graf <agraf@suse.de>
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-devel@nongnu.org,
	qemu-ppc@nongnu.org, Bharata B Rao <bharata@linux.vnet.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC 0/3] Draft implementation of HPT resizing (qemu side)
Date: Fri, 29 Jan 2016 09:09:49 +1100	[thread overview]
Message-ID: <20160128220949.GA18835@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <56AA827A.2070905@suse.de>

On Thu, Jan 28, 2016 at 10:04:58PM +0100, Alexander Graf wrote:
> 
> Does this work on real hardware? Say, a G5?

Do you mean, could a bare-metal kernel change its hashed page table?
It could - it would have to allocate a new table, copy over the bolted
mappings (at least), switch to real mode, change SDR1, switch back to
virtual mode.

Paul.

  reply	other threads:[~2016-01-28 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  5:44 [Qemu-devel] [RFC 0/3] Draft implementation of HPT resizing (qemu side) David Gibson
2016-01-18  5:44 ` [Qemu-devel] [RFC 1/3] pseries: Stub hypercalls for HPT resizing David Gibson
2016-01-18  5:44 ` [Qemu-devel] [RFC 2/3] pseries: Implement " David Gibson
2016-01-18  5:44 ` [Qemu-devel] [RFC 3/3] pseries: Advertise HPT resize capability David Gibson
2016-01-18  5:45 ` [Qemu-devel] [RFC 0/3] Draft implementation of HPT resizing (qemu side) David Gibson
2016-01-19  7:48 ` Bharata B Rao
2016-01-19 11:02   ` David Gibson
2016-01-28 21:04     ` Alexander Graf
2016-01-28 22:09       ` Paul Mackerras [this message]
2016-01-29  2:47       ` David Gibson
2016-01-29  6:18         ` Alexander Graf
2016-01-29 23:11           ` David Gibson

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=20160128220949.GA18835@fergus.ozlabs.ibm.com \
    --to=paulus@ozlabs.org \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --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).