qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: groug@kaod.org, lvivier@redhat.com, qemu-ppc@nongnu.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spapr: Remove support for explicitly allocated RMAs
Date: Thu, 3 May 2018 17:35:41 +1000	[thread overview]
Message-ID: <20180503073541.GZ13229@umbus.fritz.box> (raw)
In-Reply-To: <2bd5d47b-5561-fa4a-4277-6ef026ff8749@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

On Thu, May 03, 2018 at 09:19:34AM +0200, Thomas Huth wrote:
> On 03.05.2018 09:10, David Gibson wrote:
> > Current POWER cpus allow for a VRMA, a special mapping which describes a
> > guest's view of memory when in real mode (MMU off, from the guest's point
> > of view).  Older cpus didn't have that which meant that to support a guest
> > a special host-contiguous region of memory was needed to give the guest its
> > Real Mode Area (RMA).
> > 
> > KVM used to provide special calls to allocate a contiguous RMA for those
> > cases.  This was useful in the early days of KVM on Power to allow it to be
> > tested on PowerPC 970 chips as used in Macintosh G5 machines.  Now, those
> > machines are so old as to be almost irrelevant.
> 
> I still got my YDL PowerStation somewhere in a corner ... but well,
> true, I haven't turned on its power since a year or two... or three...
> 
> > The normal qemu deprecation process would require this to be marked
> > deprecated then removed in 2 releases.  However, this can only be used
> > with corresponding support in the host kernel - which was dropped
> > years ago (in c17b98cf "KVM: PPC: Book3S HV: Remove code for PPC970
> > processors" of 2014-12-03 to be precise).  Therefore it should be ok
> > to drop this immediately.
> 
> OK, fair.
> 
> > Just to be clear this only affects *KVM* guests with PowerPC 970, and those
> > already require an ancient host kernel.  TCG guests with PowerPC 970 should
> > still work.
> 
> Just to be sure: kvm-pr will continue to work on a 970 host, right? In
> that case:

Yes, KVM PR should be fine.  Not that I've tested, but I see no reason
it would break.  I'll clarify that in the message.

> Acked-by: Thomas Huth <thuth@redhat.com>
> 

-- 
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: 833 bytes --]

      reply	other threads:[~2018-05-03 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  7:10 [Qemu-devel] [PATCH] spapr: Remove support for explicitly allocated RMAs David Gibson
2018-05-03  7:19 ` Thomas Huth
2018-05-03  7:35   ` David Gibson [this message]

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=20180503073541.GZ13229@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --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).