From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] pci-assign: MSI affinity support
Date: Fri, 10 May 2013 14:40:04 +0200 [thread overview]
Message-ID: <518CEAA4.6090005@siemens.com> (raw)
In-Reply-To: <20130509163157.22536.68566.stgit@bling.home>
On 2013-05-09 18:35, Alex Williamson wrote:
> I posted these about 6 months ago and Jan felt we should implement
> MSI notifiers like we have for MSI-X. That still hasn't happened.
Device assignments are the only currently known users - and you provide
this feature, so...
POWER does this nice configuration of MSI messages via a side channel.
Not that it already fires the MSI-X notifiers properly, but a generic
notifier based approach is the right way to abstract away the different
modification channels (instead of encoding them at the consumer side
like in your patches).
Moreover, having different designs for MSI and MSI-X is just ugly.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-05-10 12:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 16:35 [Qemu-devel] [PATCH 0/2] pci-assign: MSI affinity support Alex Williamson
2013-05-09 16:35 ` [Qemu-devel] [PATCH 1/2] pci-assign: Refactor MSI virq array Alex Williamson
2013-05-09 16:36 ` [Qemu-devel] [PATCH 2/2] pci-assign: Add MSI affinity support Alex Williamson
2013-05-12 11:01 ` Michael S. Tsirkin
2013-05-10 12:40 ` Jan Kiszka [this message]
2013-05-10 15:47 ` [Qemu-devel] [PATCH 0/2] pci-assign: " Alex Williamson
2013-05-12 11:23 ` Michael S. Tsirkin
2013-05-22 22:59 ` Anthony Liguori
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=518CEAA4.6090005@siemens.com \
--to=jan.kiszka@siemens.com \
--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 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).