All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 5/7] qemu-kvm: Move gsi bits from kvm_msix_vector_add to kvm_msi_add_message
Date: Wed, 27 Apr 2011 16:36:00 +0300	[thread overview]
Message-ID: <20110427133600.GI15788@redhat.com> (raw)
In-Reply-To: <4DB81A2B.9020603@siemens.com>

On Wed, Apr 27, 2011 at 03:29:15PM +0200, Jan Kiszka wrote:
> On 2011-04-27 14:54, Michael S. Tsirkin wrote:
> > On Sat, Apr 23, 2011 at 12:23:38PM +0200, Jan Kiszka wrote:
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >>
> >> Testing support and allocating a GSI for an MSI message is required both
> >> for MSI and MSI-X. At this chance, drop the aging version warning.
> >>
> >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > 
> > No objection, but I do note that this means running on an old
> > kernel will lead to a silent failure.
> 
> Shouldn't be silent: The caller of msi_vector_use should check and
> process the error (virtio should even forward it to guest IIUC).

It does, but the msi/msix spec does not allow this so not
all guest OSes can use this extended reporting.

> > stderr output is not in fact much better: I think we should
> > check the capability in msix_init. Care coding this up?
> 
> I think the motivation to check on vector activation is that devices and
> guests without a need for MSI should not cause a failure if MSI is
> unsupported by KVM.
> 
> Jan

IMO it's better not to report MSI capability in this setup.


> -- 
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-04-27 13:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23 10:23 [PATCH 0/7] qemu-kvm: Clean up and enhance MSI irqchip support Jan Kiszka
2011-04-23 10:23 ` [PATCH 1/7] qemu-kvm: Drop unneeded kvm_irq_routing_entry declaration Jan Kiszka
2011-04-23 10:23 ` [PATCH 2/7] qemu-kvm: Rename kvm_msix_message to KVMMsiMessage Jan Kiszka
2011-04-27 13:34   ` Michael S. Tsirkin
2011-04-27 14:04     ` Jan Kiszka
2011-04-27 14:29       ` Avi Kivity
2011-04-27 14:30         ` Jan Kiszka
2011-04-27 14:40           ` Avi Kivity
2011-04-27 14:47             ` Jan Kiszka
2011-04-27 14:36         ` Michael S. Tsirkin
2011-04-27 14:35       ` Michael S. Tsirkin
2011-04-23 10:23 ` [PATCH 3/7] qemu-kvm: Refactor MSI core API of KVM Jan Kiszka
2011-04-23 10:23 ` [PATCH 4/7] qemu-kvm: Fix and clean up msix vector use/unuse hooks Jan Kiszka
2011-04-27 12:06   ` Michael S. Tsirkin
2011-04-23 10:23 ` [PATCH 5/7] qemu-kvm: Move gsi bits from kvm_msix_vector_add to kvm_msi_add_message Jan Kiszka
2011-04-27 12:54   ` Michael S. Tsirkin
2011-04-27 13:29     ` Jan Kiszka
2011-04-27 13:36       ` Michael S. Tsirkin [this message]
2011-04-23 10:23 ` [PATCH 6/7] qemu-kvm: Move entry comparison into kvm_msi_update_message Jan Kiszka
2011-04-23 10:23 ` [PATCH 7/7] qemu-kvm: Add in-kernel irqchip support for MSI Jan Kiszka
2011-04-27 13:31   ` Michael S. Tsirkin
2011-04-27 14:44     ` Jan Kiszka

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=20110427133600.GI15788@redhat.com \
    --to=mst@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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.