Re: [PATCH 4/5] target/rx: Load reset vector from memory after first run

2025-02-18 Thread Keith Packard via
> > By delaying the load of the reset vector to the reset_exit phase, > > you can always load from rom. > I'm not sure how -- the ROM image is discarded when it gets loaded into > read-only memory. If loaded to read-write memory, I bet it would > stay around. Ah, but by delaying until after cpu_

Re: [PATCH 4/5] target/rx: Load reset vector from memory after first run

2025-02-18 Thread Keith Packard via
> So I'm OK with this patch doing this the way it does, > except that I have one question: what's that > process_queued_cpu_work() call doing? We don't need > that on the Arm equivalent... Yup, I needed that because I was running this bit at cpu_reset_hold time, not waiting until after cpu reset

Re: [PATCH 4/5] target/rx: Load reset vector from memory after first run

2025-02-18 Thread Keith Packard via
From: Richard Henderson Date: Sat, 15 Feb 2025 10:24:05 -0800 > By delaying the load of the reset vector to the reset_exit phase, > you can always load from rom. I'm not sure how -- the ROM image is discarded when it gets loaded into read-only memory. If loaded to read-write memory, I bet it wou

Re: [PATCH 4/5] target/rx: Load reset vector from memory after first run

2025-02-17 Thread Peter Maydell
On Sat, 15 Feb 2025 at 18:24, Richard Henderson wrote: > > On 2/14/25 18:16, Keith Packard via wrote: > > The ROM images all get deleted as they've been loaded to memory, so we > > can't go fetch the reset vector from there. Instead, fetch it from > > memory. To make that work, we need to execute

Re: [PATCH 4/5] target/rx: Load reset vector from memory after first run

2025-02-15 Thread Richard Henderson
On 2/14/25 18:16, Keith Packard via wrote: The ROM images all get deleted as they've been loaded to memory, so we can't go fetch the reset vector from there. Instead, fetch it from memory. To make that work, we need to execute the delayed mmu setup function tcg_commit_cpu as that wires up memory