Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v7] RISC-V: enable XIP
To:     Mike Rapoport <rppt@linux.ibm.com>
Cc:     Alex Ghiti <alex@ghiti.fr>,
        Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-arch@vger.kernel.org, linux-mm@kvack.org,
        Vitaly Wool <vitaly.wool@konsulko.com>
References: <20210409065115.11054-1-alex@ghiti.fr>
 <3500f3cb-b660-5bbc-ae8d-0c9770e4a573@ghiti.fr>
 <be575094-badf-bac7-1629-36808ca530cc@redhat.com>
 <c4e78916-7e4c-76db-47f6-4dda3f09c871@ghiti.fr>
 <d4d771a8-c731-acaf-b42d-44800c61f2e6@redhat.com>
 <YHBgUs1JKvHWkG9F@linux.ibm.com>
From:   David Hildenbrand <david@redhat.com>
Organization: Red Hat GmbH
Message-ID: <2d442bca-c367-598c-b4ee-746925517118@redhat.com>
Date:   Fri, 9 Apr 2021 16:16:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <YHBgUs1JKvHWkG9F@linux.ibm.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 09.04.21 16:10, Mike Rapoport wrote:
> On Fri, Apr 09, 2021 at 02:07:24PM +0200, David Hildenbrand wrote:
>> On 09.04.21 13:39, Alex Ghiti wrote:
>>> Hi David,
>>
>> I assume you still somehow create the direct mapping for the kernel, right?
>> So it's really some memory region with a direct mapping but without a memmap
>> (and right now, without a resource), correct?
> 
> XIP kernel text is not a region in memory to begin with ;-)

I think that's the part that confused me. I thought it would be mapped 
somehow into physical address space and would be addressed like other 
memory -- just that reads would be rewired to go to flash.

> 
> It resides in a flash and it is executed directly from there without being
> relocated to RAM.
> 
> That's why it does not need neither direct mapping, nor struct pages.

Thanks for clarifying! :)

-- 
Thanks,

David / dhildenb