All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-1.2] msix: make [un]use vectors on reset/load optional
Date: Wed, 29 Aug 2012 18:54:35 +0200	[thread overview]
Message-ID: <503E494B.8010507@suse.de> (raw)
In-Reply-To: <20120829164056.GA7792@redhat.com>

$subject: "[un]used vectors"? -- could be fixed by committer.

/-F

Am 29.08.2012 18:40, schrieb Michael S. Tsirkin:
> The facility to use/unuse vectors dynamically is helpful
> for virtio but little else: everyone just seems to use
> vectors in their init function.
> 
> Avoid clearing msix vector use info on reset and load.
> For virtio, clear it explicitly.
> This should fix regressions reported with ivshmem - though
> I didn't test this, I verified that virtio keeps
> working like it did.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  parent reply	other threads:[~2012-08-29 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29 16:40 [Qemu-devel] [PATCH for-1.2] msix: make [un]use vectors on reset/load optional Michael S. Tsirkin
2012-08-29 16:44 ` Jan Kiszka
2012-08-29 16:47   ` Michael S. Tsirkin
2012-08-29 16:59     ` Cam Macdonell
2012-08-29 16:54 ` Andreas Färber [this message]
2012-08-29 18:13   ` Michael S. Tsirkin
2012-08-30 13:34     ` Andreas Färber
2012-08-30 14:39       ` Michael S. Tsirkin
2012-08-29 17:17 ` Cam Macdonell

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=503E494B.8010507@suse.de \
    --to=afaerber@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.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.