mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] ARM: mmu_32: fix setting up zero page when it is in SDRAM
Date: Wed, 31 May 2023 14:40:13 +0200	[thread overview]
Message-ID: <4f8e95c6-8279-b287-234c-01de2eaf7996@pengutronix.de> (raw)
In-Reply-To: <20230531123840.GB18491@pengutronix.de>

On 31.05.23 14:38, Sascha Hauer wrote:
> On Wed, May 31, 2023 at 01:58:33PM +0200, Ahmad Fatoum wrote:
>>> From b6e5c92682467496bd9c57918996f1feffda2dd6 Mon Sep 17 00:00:00 2001
>>> From: Sascha Hauer <s.hauer@pengutronix.de>
>>> Date: Wed, 31 May 2023 11:58:51 +0200
>>> Subject: [PATCH] ARM: mmu_32: fix setting up zero page when it is in SDRAM
>>>
>>> We used to skip setting the zero page to faulting when SDRAM starts at
>>> 0x0. As bootm code now explicitly sets the zero page accessible before
>>> copying ATAGs there this should no longer be necessary, so
>>> unconditionally set the zero page to faulting during MMU startup.  This
>>> also moves the zero page and vector table setup after the point the
>>> SDRAM has been mapped cachable, because otherwise the zero page and
>>> possibly the vector table mapping would be overwritten.
>>>
>>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>>> ---
>>>  arch/arm/cpu/mmu_32.c | 23 +++++++++--------------
>>>  1 file changed, 9 insertions(+), 14 deletions(-)
>>>
>>> diff --git a/arch/arm/cpu/mmu_32.c b/arch/arm/cpu/mmu_32.c
>>> index c4e5a3bb0a..14775768a3 100644
>>> --- a/arch/arm/cpu/mmu_32.c
>>> +++ b/arch/arm/cpu/mmu_32.c
>>> @@ -461,19 +461,14 @@ static int set_vector_table(unsigned long adr)
>>>  
>>>  static void create_zero_page(void)
>>
>> Is this commit incomplete? Vectors should be set up unconditionally and
>> create_zero_page should be called after it.
> 
> Vectors are set up unconditionally and create_zero_page() is called the
> same way as before.

So zero page is requested first and then on platforms with vector at
address 0 requesting fails and we are left without configured IVT?

> 
> Sascha
> 
>>
>>>  {
>>> -	struct resource *zero_sdram;
>>> +	/*
>>> +	 * In case the zero page is in SDRAM request it to prevent others
>>> +	 * from using it
>>> +	 */
>>> +	request_sdram_region("zero page", 0x0, PAGE_SIZE);
>>>  
>>> -	zero_sdram = request_sdram_region("zero page", 0x0, PAGE_SIZE);
>>> -	if (zero_sdram) {
>>> -		/*
>>> -		 * Here we would need to set the second level page table
>>> -		 * entry to faulting. This is not yet implemented.
>>> -		 */
>>> -		pr_debug("zero page is in SDRAM area, currently not supported\n");
>>> -	} else {
>>> -		zero_page_faulting();
>>> -		pr_debug("Created zero page\n");
>>> -	}
>>> +	zero_page_faulting();
>>> +	pr_debug("Created zero page\n");
>>>  }
>>>  
>>>  /*
>>> @@ -530,8 +525,6 @@ void __mmu_init(bool mmu_on)
>>>  
>>>  	pr_debug("ttb: 0x%p\n", ttb);
>>>  
>>> -	vectors_init();
>>> -
>>>  	/*
>>>  	 * Early mmu init will have mapped everything but the initial memory area
>>>  	 * (excluding final OPTEE_SIZE bytes) uncached. We have now discovered
>>> @@ -552,6 +545,8 @@ void __mmu_init(bool mmu_on)
>>>  
>>>  		remap_range((void *)pos, bank->start + bank->size - pos, MAP_CACHED);
>>>  	}
>>> +
>>> +	vectors_init();
>>>  }
>>>  
>>>  /*
>>
>> -- 
>> Pengutronix e.K.                           |                             |
>> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
>> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>>
>>
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |




  reply	other threads:[~2023-05-31 12:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 10:35 [PATCH v2 1/2] ARM: set zero page accessible before copying ATAGs there Sascha Hauer
2023-05-31 10:35 ` [PATCH v2 2/2] ARM: mmu_32: fix setting up zero page when it is in SDRAM Sascha Hauer
2023-05-31 10:45   ` Ahmad Fatoum
2023-05-31 11:21     ` Sascha Hauer
2023-05-31 11:58       ` Ahmad Fatoum
2023-05-31 12:38         ` Sascha Hauer
2023-05-31 12:40           ` Ahmad Fatoum [this message]
2023-06-01  6:46             ` Sascha Hauer
2023-06-01  7:00               ` Ahmad Fatoum
2023-05-31 10:40 ` [PATCH v2 1/2] ARM: set zero page accessible before copying ATAGs there Ahmad Fatoum

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=4f8e95c6-8279-b287-234c-01de2eaf7996@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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