kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] qemu-kvm: Do not advertise MSI caps on lacking KVM support
Date: Tue, 3 May 2011 16:18:40 -0300	[thread overview]
Message-ID: <20110503191840.GC10617@amt.cnet> (raw)
In-Reply-To: <4DBAA001.3000905@siemens.com>

On Fri, Apr 29, 2011 at 01:24:49PM +0200, Jan Kiszka wrote:
> As suggested by Michael Tsirkin: Move the check for GSI routing from
> kvm_msi_message_add to the MSI/MSI-X initalization. If it fails (and KVM
> is in in-kernel irqchip mode), do not advertise MSI at all.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Applied, thanks.


      reply	other threads:[~2011-05-03 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 11:24 [PATCH] qemu-kvm: Do not advertise MSI caps on lacking KVM support Jan Kiszka
2011-05-03 19:18 ` Marcelo Tosatti [this message]

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=20110503191840.GC10617@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@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 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).