qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] spapr: make sure RMA is in first mode of first


From: Alexey Kardashevskiy
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
User-agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0

On 11/05/2013 12:19 AM, Peter Maydell wrote:
> On 4 November 2013 13:11, Alexey Kardashevskiy <address@hidden> 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 via email to

[Prev in Thread] Current Thread [Next in Thread]