Re: [Qemu-devel] Questions about the flow of interrupt simulation

here is any documents or tutorial about interrupt, please share with me, I am willing to study it. Sincerely, Eva 2018-05-24 21:40 GMT+08:00 Peter Maydell : > On 23 May 2018 at 11:45, Eva Chen wrote: > > Hi, > > > > I have added a new virtual device under qemu/hw, and a d

[Qemu-devel] Questions about the flow of interrupt simulation

Hi, I have added a new virtual device under qemu/hw, and a device driver in the source code of guest OS (I use arm linux). Since I want to add an interrupt to the virtual device, I am tracing the flow of interrupt simulation of QEMU. However, I have some questions about the flow of interrupt, and

[Qemu-devel] Question about io_writex()

Hello, I want to know the flow of how devices read/write function be called by code_gen_buffer(). Take pl110_write() for example, I set a breakpoint in pl110_write(), and the backtrace shows bellow. (gdb) #0 * pl110_write* (opaque=0x56e8f3f0, offset=28, val=0, size=4) at hw/display/pl110.c:3

[Qemu-devel] Let event loop use non-default GMainContext

Hello, It seems that AIO use global default GMainContext by *g_main_context_default()*. I want to replace all default GMainContext into another GMainContext by *g_main_context_new()*, but I have no idea when and where to add *g_main_context_new()*. It should be only created new GMainContext once,

[Qemu-devel] qemu 2.10.2 : util/qemu-thread-posix.c: 64: qemu_mutex_lock: Assertion 'mutex->initialized' failed

Hello, I am working on compiling QEMU 2.10.2 to a static library. Everything works fine in compiling QEMU to an execution file(qemu-system-aarch64), but after I link all .o and .a file to create a QEMU library and write a c file to call qemu_main() in qemu/util/vl.c(I have changed the name "main(