From: bill4carson@gmail.com (bill4carson)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about ARM interrupt virtualization
Date: Fri, 16 Sep 2011 14:13:34 +0800 [thread overview]
Message-ID: <4E72E90E.7060906@gmail.com> (raw)
Hi, all
I have been doing ARM interrupt virtualization based on Christoffer KVM
work.
Current status is an A15 guest os could boot successfully based on ARM KVM
without interrupt virtualization.
Interrupt injection is taken care of by Qemu, if interrupt
virtualization need to be
supported, then all the gic cpu interface code in Qemu must be removed.
The distributor in Qemu figure out the best irq, then ship this best_irq
into virtual
cpu interface through list register.
The problem is Distributor state must be synchronized with two cpu
interface
actions: ACK(interrupt acknowledge) and EOI (end Of Interrupt).
EOI could be trapped by hypervisor, this will enable us to call
gic_complete_irq
in Qemu to update Distributor state.
However for now I cannot find a way for ACK to be catch,
or am I missing something important here?
Any tips/suggestions would be appreciated!
bill
reply other threads:[~2011-09-16 6:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E72E90E.7060906@gmail.com \
--to=bill4carson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).