qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] MSI: Robust resource release
Date: Thu, 5 May 2011 16:10:19 +0300	[thread overview]
Message-ID: <20110505131019.GE30119@redhat.com> (raw)
In-Reply-To: <4DBEF14F.3010505@siemens.com>

On Mon, May 02, 2011 at 08:00:47PM +0200, Jan Kiszka wrote:
> msi_init may fail, so we need to check on uninit if the cap was
> actually installed. This also avoids that the users need to check.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>

Applied, thanks!

> ---
>  hw/ide/ich.c   |    5 +----
>  hw/intel-hda.c |    4 +---
>  hw/msi.c       |   12 ++++++++++--
>  3 files changed, 12 insertions(+), 9 deletions(-)
> 
> v2: Push cap check into msi_uninit (just like msix), remove check from
>     users.
> 
> diff --git a/hw/ide/ich.c b/hw/ide/ich.c
> index a3d475c..8c1ff6c 100644
> --- a/hw/ide/ich.c
> +++ b/hw/ide/ich.c
> @@ -110,10 +110,7 @@ static int pci_ich9_uninit(PCIDevice *dev)
>      struct AHCIPCIState *d;
>      d = DO_UPCAST(struct AHCIPCIState, card, dev);
>  
> -    if (msi_enabled(dev)) {
> -        msi_uninit(dev);
> -    }
> -
> +    msi_uninit(dev);
>      qemu_unregister_reset(ahci_reset, d);
>      ahci_uninit(&d->ahci);
>  
> diff --git a/hw/intel-hda.c b/hw/intel-hda.c
> index b0b1d12..093c4b9 100644
> --- a/hw/intel-hda.c
> +++ b/hw/intel-hda.c
> @@ -1174,9 +1174,7 @@ static int intel_hda_exit(PCIDevice *pci)
>  {
>      IntelHDAState *d = DO_UPCAST(IntelHDAState, pci, pci);
>  
> -    if (d->msi) {
> -        msi_uninit(&d->pci);
> -    }
> +    msi_uninit(&d->pci);
>      cpu_unregister_io_memory(d->mmio_addr);
>      return 0;
>  }
> diff --git a/hw/msi.c b/hw/msi.c
> index 0cbf89f..3141804 100644
> --- a/hw/msi.c
> +++ b/hw/msi.c
> @@ -183,9 +183,17 @@ int msi_init(struct PCIDevice *dev, uint8_t offset,
>  
>  void msi_uninit(struct PCIDevice *dev)
>  {
> -    uint16_t flags = pci_get_word(dev->config + msi_flags_off(dev));
> -    uint8_t cap_size = msi_cap_sizeof(flags);
> +    uint16_t flags;
> +    uint8_t cap_size;
> +
> +    if (!(dev->cap_present & QEMU_PCI_CAP_MSI)) {
> +        return;
> +    }
> +    flags = pci_get_word(dev->config + msi_flags_off(dev));
> +    cap_size = msi_cap_sizeof(flags);
>      pci_del_capability(dev, PCI_CAP_ID_MSIX, cap_size);
> +    dev->cap_present &= ~QEMU_PCI_CAP_MSI;
> +
>      MSI_DEV_PRINTF(dev, "uninit\n");
>  }
>  
> -- 
> 1.7.1

      parent reply	other threads:[~2011-05-05 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02  9:13 [Qemu-devel] [PATCH] MSI: Fix release of resources Jan Kiszka
2011-05-02 18:00 ` [Qemu-devel] [PATCH v2] MSI: Robust resource release Jan Kiszka
2011-05-03 10:16   ` Alexander Graf
2011-05-05 13:10   ` Michael S. Tsirkin [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=20110505131019.GE30119@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=kraxel@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).