#qemu — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #qemu, aggregated by home.social.
-
'MRMCD2026 - Über die Grenzen von Proxmox hinaus: Selber VMs mit QEMU basteln' https://www.youtube.com/watch?v=lH8OzTA-FKg /via @xje4 #qemu #linux
-
It looks like my #aiagents file finally got into #qemu. Hopefully it will have some effect: https://gitlab.com/qemu-project/qemu/-/commit/3ab8a15569afa9ffd89971dff34d0636d48cae3c
-
I will attend the ESA Industry Space Days next week. I would be happy to meet and discuss our #RTEMS, #Linux, #NuttX, communication, #canbus, #SpaceWire, IP cores related work. Some examples
- for RTEMS CAN/CAN FD, there is near to merge Ti AM335x suport, result of this year Ning Zhang #GSoC
- motion control at #PiKRON (used by ESA for #satellite tracking and for LISA ground experiment), and at #CVUT (SaMoCon)
- for rapid prototyping CTU Simulink™ support for Linux and NuttX which can be easily extended for RTEMS and open-source pysimCoder which already target Linux, NuttX and RTEMS (ongoing preparation for Ahmad Hisham’ s thesis)
- the CTU CAN FD IP core is already available on mass produced MCU COTS silicon in addition to multiple FPGA applications including space ones
- RTEMS LwIP port started as our experiment during Premysl Houdek’s thesis and #GSoC is getting traction and was used at docking computer during Artems II mission (by the way, there will be presentation about the mission at #cvutfel by Milan Halousek at Sptember 24) and is used on TMS570 and ESP32C3 RTEMS ports
- our SumInt ADC conversion principle used in our HPLC instruments and tested at #nanoXplore for ESA which can have interesting potential for space silicon
- our NuttX support for IEEE 802.3cg 10BASE−T1S Open Alliance SPI MACPHY can be ported to RTEMS etc.
- I offer support for CAN/CAN FD emulation on #QEMU, #FlexCAN added this year
- lot of our other real-time work for Linux, NuttX and RTEMS, se my university Open Technologies Research Education and Exchange Services topics and theses lists
- we invest lot into #RISCV education at CTU, see our https://comparch.edu.cvut.cz/ pages with #QtRvSim emulator and our HDL education and sometimes even practically used cores and experiments
I arrive to Noordwijk around the lunch time on Tuesday September 15 and stay there to about 2 PM on Friday so there is lot of options to meet.
-
Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.
-
Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.
-
Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.
-
Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.
-
Here is another in a series of attempts to divine information from #qemu's issue tracker. I think this is showing that #AI #bugpocolypse reports tend to be verbose, a lot of sanitizer reports are probably mislabelled (quite often the agent will show the failure in a sanitized build) and having a decent test case correlates well with undeclared agent use. The "normal" size of reports for each class of device in (Untagged) for any tooling or TestCase.
-
The open-issue emotional roller coaster. 🎢
Hooray, there's an issue for this... oh no, it's been open since 2021! Issue affects nested #qemu virtualisation with #FreeBSD: https://gitlab.com/qemu-project/qemu/-/work_items/337
-
Написал свой ассемблер, чтобы понять, откуда берётся ff010113. Почти половину моей программы он выдумывает
Написал свой ассемблер, чтобы понять, откуда в дизассемблере берётся ff010113. Заодно посчитал, сколько строк моей программы процессор вообще не умеет исполнять, и проверил это на четырёх наборах команд, включая живой ESP32 на столе. На кристалле первая программа серии сломалась: она пишет в UART быстрее, чем провод успевает передавать, и в эмуляторе этого не видно. Что сказала плата?
https://habr.com/ru/articles/1076022/
#RISCV #ассемблер #кодирование_инструкций #псевдоинструкции #RV32I #компоновщик #релокация #bare_metal #QEMU
