qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
	qemu-stable@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v3 0/8] msi: Refactorings and reset fixes
Date: Fri, 11 May 2012 11:42:33 -0300	[thread overview]
Message-ID: <cover.1336747349.git.jan.kiszka@siemens.com> (raw)

v3 is v2 - xhci changes as MSI is instable there anyway. So, only
patches 1 and 2 are for 1.1/stable now.

CC: Alexander Graf <agraf@suse.de>
CC: Gerd Hoffmann <kraxel@redhat.com>
CC: Isaku Yamahata <yamahata@valinux.co.jp>
CC: qemu-stable@nongnu.org

Jan Kiszka (8):
  ahci: Fix reset of MSI function
  intel-hda: Fix reset of MSI function
  ahci: Clean up reset functions
  msi: Guard msi_reset with msi_present
  msi: Invoke msi/msix_reset from PCI core
  msi: Guard msi/msix_write_config with msi_present
  msi: Invoke msi/msix_write_config from PCI core
  msi: Use msi/msix_present more consistently

 hw/ide/ahci.c           |   25 +++++++++++++++----------
 hw/ide/ahci.h           |    2 +-
 hw/ide/ich.c            |   19 ++++++++-----------
 hw/intel-hda.c          |   12 ------------
 hw/ioh3420.c            |    3 +--
 hw/msi.c                |   11 ++++++++---
 hw/msix.c               |   15 +++++++++------
 hw/pci.c                |    8 ++++++++
 hw/pci_bridge.c         |    4 ++++
 hw/virtio-pci.c         |    3 ---
 hw/xio3130_downstream.c |    3 +--
 hw/xio3130_upstream.c   |    3 +--
 12 files changed, 56 insertions(+), 52 deletions(-)

-- 
1.7.3.4

             reply	other threads:[~2012-05-11 14:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 14:42 Jan Kiszka [this message]
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 1/8] ahci: Fix reset of MSI function Jan Kiszka
2012-05-22 10:17   ` Alexander Graf
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 2/8] intel-hda: " Jan Kiszka
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 3/8] ahci: Clean up reset functions Jan Kiszka
2012-05-22 10:20   ` Alexander Graf
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 4/8] msi: Guard msi_reset with msi_present Jan Kiszka
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 5/8] msi: Invoke msi/msix_reset from PCI core Jan Kiszka
2012-05-15 23:09   ` [Qemu-devel] [PATCH v4 " Jan Kiszka
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 6/8] msi: Guard msi/msix_write_config with msi_present Jan Kiszka
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 7/8] msi: Invoke msi/msix_write_config from PCI core Jan Kiszka
2012-05-11 14:42 ` [Qemu-devel] [PATCH v3 8/8] msi: Use msi/msix_present more consistently Jan Kiszka
2012-06-04 14:48   ` Michael S. Tsirkin
2012-06-04 14:53     ` [Qemu-devel] [PATCH v4 " Jan Kiszka
2012-06-04 18:57       ` Michael S. Tsirkin
2012-05-22 10:16 ` [Qemu-devel] [PATCH v3 0/8] msi: Refactorings and reset fixes Alexander Graf
2012-06-04 14:17 ` Jan Kiszka
2012-06-04 14:27   ` 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=cover.1336747349.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=agraf@suse.de \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=yamahata@valinux.co.jp \
    /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).