public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	linux-kernel@vger.kernel.org,
	David Vrabel <david.vrabel@citrix.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] xen-pciback: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Mon, 24 Feb 2014 14:18:31 -0500	[thread overview]
Message-ID: <20140224191831.GA7056@phenom.dumpdata.com> (raw)
In-Reply-To: <20140221165340.GG17353@dhcp-26-207.brq.redhat.com>

On Fri, Feb 21, 2014 at 05:53:40PM +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range()  or pci_enable_msi_exact()
> and pci_enable_msix_range() or pci_enable_msix_exact()
> interfaces.

What is this based on? Thanks.

> 
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: David Vrabel <david.vrabel@citrix.com>
> Cc: linux-pci@vger.kernel.org
> ---
>  drivers/xen/xen-pciback/pciback_ops.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/xen/xen-pciback/pciback_ops.c b/drivers/xen/xen-pciback/pciback_ops.c
> index 64eb0cd..929dd46 100644
> --- a/drivers/xen/xen-pciback/pciback_ops.c
> +++ b/drivers/xen/xen-pciback/pciback_ops.c
> @@ -213,8 +213,7 @@ int xen_pcibk_enable_msix(struct xen_pcibk_device *pdev,
>  		entries[i].vector = op->msix_entries[i].vector;
>  	}
>  
> -	result = pci_enable_msix(dev, entries, op->value);
> -
> +	result = pci_enable_msix_exact(dev, entries, op->value);
>  	if (result == 0) {
>  		for (i = 0; i < op->value; i++) {
>  			op->msix_entries[i].entry = entries[i].entry;
> -- 
> 1.7.7.6
> 
> -- 
> Regards,
> Alexander Gordeev
> agordeev@redhat.com

  parent reply	other threads:[~2014-02-24 19:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 10:15 [PATCH] xen-pciback: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19 15:22 ` Boris Ostrovsky
2014-02-19 15:40   ` Boris Ostrovsky
2014-02-19 16:05     ` Alexander Gordeev
2014-02-19 16:24       ` Boris Ostrovsky
2014-02-21 16:52         ` Alexander Gordeev
2014-02-21 16:53           ` [PATCH v2] xen-pciback: Use pci_enable_msix_exact() " Alexander Gordeev
2014-02-21 17:02             ` Alexander Gordeev
2014-02-21 18:33             ` Boris Ostrovsky
2014-02-21 18:58               ` Alexander Gordeev
2014-02-21 19:09                 ` Boris Ostrovsky
2014-02-21 21:15                   ` Konrad Rzeszutek Wilk
2014-02-24 19:18             ` Konrad Rzeszutek Wilk [this message]
2014-02-25  8:32               ` Alexander Gordeev

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=20140224191831.GA7056@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=agordeev@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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