All of lore.kernel.org
 help / color / mirror / Atom feed
* Problem with ivshmem doobell interrupt
@ 2020-07-20 23:33 Pratik Pranav
  0 siblings, 0 replies; only message in thread
From: Pratik Pranav @ 2020-07-20 23:33 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]

Hi,

My name is Pratik Pranav,  a second-year undergraduate student,
majoring in Computer
Science at Indian Institute of Technology(IIT), Delhi. I am currently
working on building a messaging layer between two VMs(x86 and ARM) using
ivshmem(rev 1) and currently deploying on QEMU.


I am facing a problem while registering an interrupt in doorbell registers.
Whenever I am registering an interrupt on doorbell-registers, I can see the
interrupt handler run when the interrupt is registered from ARM to x86, but
not from x86 to ARM. Although I think interrupts are reaching the ARM VM
concluded from the following output obtained by changing IVSHMEM_DEBUG to 1
in ivshmem.c.


-------------------------------------------------------------

IVSHMEM: interrupt on vector 0x56430d1ce940 3

IVSHMEM: interrupt on vector 0x56430d1ce940 2

IVSHMEM: interrupt on vector 0x56430d1ce940 1

IVSHMEM: interrupt on vector 0x56430d1ce940 0

-------------------------------------------------------------


All the interrupt lines are visible in /proc/interrupts in both the VMs
with MSIX enabled.


I am adding the sample code on which I am working right now. Its a simple
code just for checking whether interrupts work.


The command prompts I am using currently are:


x86: sudo qemu/x86_64-softmmu/qemu-system-x86_64 *--enable-kvm* -m 2048
-smp 4 *-chardev socket,path=/tmp/ivshmem_socket,id=foo -device
ivshmem-doorbell,chardev=foo,vectors=4* -hda x86.img -netdev
tap,id=x86nic,ifname=tap0 -device e1000,netdev=x86nic,mac=52:54:00:12:34:60
-nographic


arm: sudo qemu/aarch64-softmmu/qemu-system-aarch64 -cpu cortex-a57
-smp 2 *-chardev
socket,path=/tmp/ivshmem_socket,id=foo -device
ivshmem-doorbell,chardev=foo,vectors=4*  -m 2048 -M virt -bios qemu_efi.fd
-drive if=none,file=arm.img,id=hd0 -device virtio-blk-device,drive=hd0
-netdev tap,id=armnic,ifname=tap1 -device
e1000,netdev=armnic,mac=52:54:00:12:34:63 -nographic


Could you suggest anything?

I will be highly thankful to you.


Thank you for your consideration.

Keenly awaiting your reply,

Yours Sincerely,

Pratik Pranav

Second-Year Undergraduate

Computer Science and Technology

Indian Institute of Technology(IIT), Delhi


[image: photo]
Pratik Pranav
Student, Computer Science and Engineering at  Indian Institute of
Technology, Delhi
A  Satpura Hostel, IIT Delhi, Hauz Khas, New Delhi-110016
M  8936051771  <8936051771>
E  cs1180368@cse.iitd.ac.in  <cs1180368@cse.iitd.ac.in>
<http://www.linkedin.com/in/pratik-pranav-92629616b/>

[-- Attachment #2: Type: text/html, Size: 12121 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2020-07-21  0:53 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-20 23:33 Problem with ivshmem doobell interrupt Pratik Pranav

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.