Re: [PATCH v6 01/21] softmmu: split off vl.c:main() into main.c

2020-01-05 Thread Alexander Bulekov
On 200103 0958, Stefan Hajnoczi wrote: > On Fri, Nov 29, 2019 at 09:34:36PM +, Oleinik, Alexander wrote: > > @@ -3853,7 +3834,7 @@ int main(int argc, char **argv, char **envp) > > set_memory_options(&ram_slots, &maxram_size, machine_class); > > > > os_daemonize(); > > -rcu_disab

Re: [PATCH v6 01/21] softmmu: split off vl.c:main() into main.c

2020-01-03 Thread Stefan Hajnoczi
On Fri, Nov 29, 2019 at 09:34:36PM +, Oleinik, Alexander wrote: > @@ -3853,7 +3834,7 @@ int main(int argc, char **argv, char **envp) > set_memory_options(&ram_slots, &maxram_size, machine_class); > > os_daemonize(); > -rcu_disable_atfork(); > +/* rcu_disable_atfork(); */ >

[PATCH v6 01/21] softmmu: split off vl.c:main() into main.c

2019-11-29 Thread Oleinik, Alexander
A program might rely on functions implemented in vl.c, but implement its own main(). By placing main into a separate source file, there are no complaints about duplicate main()s when linking against vl.o. For example, the virtual-device fuzzer uses a main() provided by libfuzzer, and needs to perfo