qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	"list@suse.de:PReP" <qemu-ppc@nongnu.org>,
	Thomas Huth <thuth@linux.vnet.ibm.com>,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] spapr: make sure RMA is in first mode of first memory node
Date: Tue, 05 Nov 2013 00:35:12 +1100	[thread overview]
Message-ID: <5277A290.1050300@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA8E98h_J5BBejwcvnHn7qyYRXnvVv6mPf20p38sdvMPGQ@mail.gmail.com>

On 11/05/2013 12:19 AM, Peter Maydell wrote:
> On 4 November 2013 13:11, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>> PAPR says in "Hypervisor Call Functions":
>>
>> "Logical addresses start at zero. When control is initially passed to the
>> OS from the platform, the first region is the
>> single RMA. The first region has logical region identifier of zero. This
>> first region is specified by the first address -
>> length pair of the “reg” property of the /memory node of the OF device tree."
>>
>>
>> Question about english - is "the single RMA" equal to "the only RMA"?
> 
> No. "the single RMA" is weird English and to me implies
> that it's a term that's been defined earlier or at least
> that there is some surrounding context that would make it
> make more sense (eg some contrasting definition of
> "single RMA" vs "double RMA").


Oh. Some more context then:

"14.1.1 Real Mode Accesses
When the OS controlling an LPAR runs with address translation turned off
(MSRDR or MSRIR bit(s) =0) (real mode)
the LPAR hardware translates the memory addresses to an LPAR unique area
known as the Real Mode Area (RMA).
When control is initially passed to the OS from the platform, the RMA
starts at the LPAR's logical address 0 and is the
first logical memory block reported in the LPAR’s device tree. In general,
the RMA is a subset of the LPAR's logical
address space. Attempting a non relocated access beyond the bounds of the
RMA results in an storage interrupt
(ISI/DSI depending upon instruction or data reference). The RMA hardware
translation scheme is platform dependent.
The options are given below."


-- 
Alexey

  reply	other threads:[~2013-11-04 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 10:21 [Qemu-devel] [PATCH] spapr: make sure RMA is in first mode of first memory node Alexey Kardashevskiy
2013-11-04 10:44 ` Alexander Graf
2013-11-04 10:55   ` Benjamin Herrenschmidt
2013-11-04 11:28     ` Alexander Graf
2013-11-04 11:50       ` Thomas Huth
2013-11-04 13:11         ` Alexey Kardashevskiy
2013-11-04 13:19           ` Peter Maydell
2013-11-04 13:35             ` Alexey Kardashevskiy [this message]
2013-11-04 22:29           ` Benjamin Herrenschmidt

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=5277A290.1050300@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@linux.vnet.ibm.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).