From: Alex Williamson <alex.williamson@redhat.com>
To: mst@redhat.com
Cc: alex.williamson@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH 0/2] msix: couple fixes
Date: Fri, 22 Oct 2010 14:31:45 -0600 [thread overview]
Message-ID: <20101022193845.10161.52907.stgit@s20.home> (raw)
I've been porting the qemu vfio driver to use the common msix
infrastructure and hit a couple issues. The first patch addresses
the problem that a device may already have MSI-X capability setup
and non-adjustable BARs, so msix_init should be able to use the
existing capability instead of adding it's own.
I'm surprised we need the second patch, as I'm not sure how things
work today without it. We allocate msix_irq_entries within a
KVM_CAP_IRQCHIP #ifdef. This should be pulled in from kvm.h, if we
have CONFIG_KVM, but that's pulled in from config-target.h, which
we don't include. We can add config.h to msix.c, but that only
works if the msix object is in Makefile.target instead of
Makefile.objs. Feel free to fix this differently, but I think
something is wrong there. Thanks,
Alex
---
Alex Williamson (2):
msix: Pull in config.h for CONFIG_KVM
msix: Allow msix_init on a device with existing MSI-X capability
Makefile.objs | 2 --
Makefile.target | 1 +
hw/msix.c | 68 ++++++++++++++++++++++++++++++++-----------------------
3 files changed, 40 insertions(+), 31 deletions(-)
next reply other threads:[~2010-10-22 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 20:31 Alex Williamson [this message]
2010-10-22 20:40 ` [Qemu-devel] [PATCH 1/2] msix: Allow msix_init on a device with existing MSI-X capability Alex Williamson
2010-10-23 16:18 ` [Qemu-devel] " Michael S. Tsirkin
2010-10-23 16:55 ` Alex Williamson
2010-10-28 15:00 ` Avi Kivity
2010-11-01 15:56 ` Alex Williamson
2010-10-22 20:40 ` [Qemu-devel] [PATCH 2/2] msix: Pull in config.h for CONFIG_KVM Alex Williamson
2010-10-23 1:50 ` [Qemu-devel] " Alex Williamson
2010-10-23 7:41 ` Paolo Bonzini
2010-10-23 16:16 ` Michael S. Tsirkin
2010-10-23 16:52 ` Alex Williamson
2010-10-23 17:29 ` Michael S. Tsirkin
2010-10-23 18:42 ` Alex Williamson
2010-10-23 20:38 ` Michael S. Tsirkin
2010-10-23 21:01 ` Alex Williamson
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=20101022193845.10161.52907.stgit@s20.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).