From: Jan Kiszka <jan.kiszka@web.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH] msix: Support specifying offsets, BARs, and capability location
Date: Sun, 10 Jun 2012 19:15:42 +0200 [thread overview]
Message-ID: <4FD4D63E.5020602@web.de> (raw)
In-Reply-To: <20120610165957.3942.89495.stgit@bling.home>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
On 2012-06-10 19:02, Alex Williamson wrote:
> msix_init has very little configurability as to how it lays out
> MSI/X for a device. It claims to resize BARs, but doesn't
> actually do this anymore. This patch allows MSI/X to be fully
> specified, which is necessary both for emulated devices trying
> to match the physical layout of a hardware device as well as for
> any kind of device assignment.
>
> The original intent of msix_init seems to have been to allow
> completely virtual devices so enable MSI/X without knowing
> anything about it. A sort of "here's a BAR and a device, add
> MSI/X to it". We've already dropped the resize support with
> the memory API, and I think it makes sense to tune the interface
> to something that still makes it easy for virtual devices to use,
> but allows the full specification for realistically creating
> emulated devices using MSI/X.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> This needs more testing, but I wanted to send it out in case someone
> else is working on something similar. In order to not modify the
> generic capability adding code VFIO needs to tell qemu about ever
> capability for a device. The main roadblock to doing that is that
> msix_init does not provide sufficient specification of the MSI/X area
> to match a physical device. This solves that.
Reminds me that you asked for my version:
http://git.kiszka.org/?p=qemu.git;a=shortlog;h=refs/heads/queues/msi
specifically the top two commits. WIP, just picked the old commits,
result untested.
Still need to look into your version.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-06-10 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 17:02 [Qemu-devel] [RFC PATCH] msix: Support specifying offsets, BARs, and capability location Alex Williamson
2012-06-10 17:15 ` Jan Kiszka [this message]
2012-06-10 17:48 ` Michael S. Tsirkin
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=4FD4D63E.5020602@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--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 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.