From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: [kvm-ppc-devel] PCI interrupts
Date: Mon, 03 Mar 2008 05:56:48 +0000 [thread overview]
Message-ID: <1204523808.5581.11.camel@basalt> (raw)
Despite the fact that we seem to have UART interrupts going missing, I
tried playing with attaching a qemu PCI device (rtl8139) to a KVM 440
guest to see what would happen. First though I had to fix some poorly
considered endian-handling qemu code, but after that "ip=dhcp" kernel
parameter still doesn't work (ifup succeeds; DHCP fails).
Debugging reveals that slirp (qemu's "user networking") does in fact see
the DHCP request, and the rtl8139 code does in fact see the reply, but
somehow qemu and the guest seem to disagree about which IRQ to expect
the interrupt on. Hacking it so that they agree doesn't seem to fix the
problem either, so right now I'm digging in to qemu's UIC emulation to
see if there's an issue there. Right now I'm not certain if the guest is
properly setting polarity (UIC0_PR), but more investigation is needed.
Anyways, as an alternative for now, we may be able to get VirtIO working
if we add a polling mode. It might be as easy as setting up a timer in
virtio_pci.c that calls vp_interrupt() directly...
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
reply other threads:[~2008-03-03 5:56 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=1204523808.5581.11.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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 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.