Re: [PATCH 1/3] riscv: Unify Qemu's reset vector code path

2020-06-19 Thread Atish Patra
On Fri, Jun 19, 2020 at 10:11 AM Alexander Richardson wrote: > > On Tue, 16 Jun 2020 at 20:30, Atish Patra wrote: > > > > Currently, all riscv machines have identical reset vector code > > implementations with memory addresses being different for all machines. > > They can be easily combined

Re: [PATCH 1/3] riscv: Unify Qemu's reset vector code path

2020-06-19 Thread Alexander Richardson
On Tue, 16 Jun 2020 at 20:30, Atish Patra wrote: > > Currently, all riscv machines have identical reset vector code > implementations with memory addresses being different for all machines. > They can be easily combined into a single function in common code. > > Move it to common function and let

Re: [PATCH 1/3] riscv: Unify Qemu's reset vector code path

2020-06-18 Thread Atish Patra
On Thu, Jun 18, 2020 at 1:03 AM Bin Meng wrote: > > On Wed, Jun 17, 2020 at 3:30 AM Atish Patra wrote: > > > > Currently, all riscv machines have identical reset vector code > > implementations with memory addresses being different for all machines. > > They can be easily combined into a single

Re: [PATCH 1/3] riscv: Unify Qemu's reset vector code path

2020-06-18 Thread Bin Meng
On Wed, Jun 17, 2020 at 3:30 AM Atish Patra wrote: > > Currently, all riscv machines have identical reset vector code > implementations with memory addresses being different for all machines. > They can be easily combined into a single function in common code. > > Move it to common function and

[PATCH 1/3] riscv: Unify Qemu's reset vector code path

2020-06-16 Thread Atish Patra
Currently, all riscv machines have identical reset vector code implementations with memory addresses being different for all machines. They can be easily combined into a single function in common code. Move it to common function and let all the machines use the common function. Signed-off-by: