Re: [RFC v3 4/4] cpus: extract out accel-specific code to each accel

2020-05-27 Thread Claudio Fontana
Ciao Roman, thanks for looking at this and trying it out, On 5/26/20 9:16 PM, Roman Bolshakov wrote: > On Mon, May 25, 2020 at 04:54:40PM +0200, Claudio Fontana wrote: >> each accelerator registers a new "CpusAccelInterface" >> on initialization, providing functions for starting a vcpu, >>

Re: [RFC v3 4/4] cpus: extract out accel-specific code to each accel

2020-05-26 Thread Roman Bolshakov
On Mon, May 25, 2020 at 04:54:40PM +0200, Claudio Fontana wrote: > each accelerator registers a new "CpusAccelInterface" > on initialization, providing functions for starting a vcpu, > kicking a vcpu, and sychronizing state. > > This way the code in cpus.cc is now all general softmmu code, >

Re: [RFC v3 4/4] cpus: extract out accel-specific code to each accel

2020-05-25 Thread Claudio Fontana
On 5/25/20 5:22 PM, Philippe Mathieu-Daudé wrote: > On 5/25/20 4:54 PM, Claudio Fontana wrote: >> each accelerator registers a new "CpusAccelInterface" >> on initialization, providing functions for starting a vcpu, >> kicking a vcpu, and sychronizing state. >> >> This way the code in cpus.cc is

Re: [RFC v3 4/4] cpus: extract out accel-specific code to each accel

2020-05-25 Thread Philippe Mathieu-Daudé
On 5/25/20 4:54 PM, Claudio Fontana wrote: > each accelerator registers a new "CpusAccelInterface" > on initialization, providing functions for starting a vcpu, > kicking a vcpu, and sychronizing state. > > This way the code in cpus.cc is now all general softmmu code, > nothing (or almost

[RFC v3 4/4] cpus: extract out accel-specific code to each accel

2020-05-25 Thread Claudio Fontana
each accelerator registers a new "CpusAccelInterface" on initialization, providing functions for starting a vcpu, kicking a vcpu, and sychronizing state. This way the code in cpus.cc is now all general softmmu code, nothing (or almost nothing) accelerator-specific anymore. Signed-off-by: Claudio