<[email protected]> escreveu no dia segunda, 20/11/2023 à(s) 18:41:
> > > > > > Are you sure this works in the majority of scenarios? > > > Last time I worked on this qemu user mode failed to run > > > multithreading applications. > > > > > > > > > Sorry, I was wrong above. > > The issue was not multithreading but with the fork system call. > > > > Hi Jose > > I was using it for running Unit Tests on the host before I deployed > them to the target device as ptest. This worked well. It is well > integrated with cmake and therefore also with IDEs. So I thought that > there are certain use cases where it would be nice to have it opt-in. > > meson offers qemu-user as well (because of gobject). So if qemu-user is > not usable there will be other challenges as well. > > There is also a MACHINE_FEATURE which allows to support it for ARCHs > where it works well but not for ARCHs where qemu-user is known to be > broken. > > I think it would be a nice optional feature. > I agree without any doubt on that part. But I believe this doesn't work for applications that are using the fork system call. So consider this will also break any ptest using fork, giving the wrong impression the test is failing. Here is my attempt to add support in meson to run the ptest at build time. https://lists.openembedded.org/g/openembedded-core/topic/89289917 Jose > > Regards, > Adrian > -- Best regards, José Quaresma
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#190964): https://lists.openembedded.org/g/openembedded-core/message/190964 Mute This Topic: https://lists.openembedded.org/mt/102708283/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
