All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v2] xen: add support for MSI message groups
Date: Fri, 28 Feb 2014 18:46:23 +0100	[thread overview]
Message-ID: <5310CB6F.1070706__25525.6242388443$1393609693$gmane$org@citrix.com> (raw)
In-Reply-To: <5310C54A.1080906@oracle.com>

On 28/02/14 18:20, Boris Ostrovsky wrote:
> On 02/27/2014 01:45 PM, Boris Ostrovsky wrote:
>> On 02/27/2014 01:15 PM, Roger Pau Monne wrote:
>>> Add support for MSI message groups for Xen Dom0 using the
>>> MAP_PIRQ_TYPE_MULTI_MSI pirq map type.
>>>
>>> In order to keep track of which pirq is the first one in the group all
>>> pirqs in the MSI group except for the first one have the newly
>>> introduced PIRQ_MSI_GROUP flag set. This prevents calling
>>> PHYSDEVOP_unmap_pirq on them, since the unmap must be done with the
>>> first pirq in the group.
>>
>> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>>
>>
> 
> 
> I was just looking at xen_setup_msi_irqs() (for a different reason) and
> I am no longer sure this patch does anything:
> 
> static int xen_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
> {
>         int irq, ret, i;
>         struct msi_desc *msidesc;
>         int *v;
> 
>         if (type == PCI_CAP_ID_MSI && nvec > 1)
>                 return 1;
> ....
> 
> Same thing for xen_hvm_setup_msi_irqs().

As said in the commit message this is only for Dom0, so the function
modified is xen_initdom_setup_msi_irqs (were this check is removed).

Roger.

  reply	other threads:[~2014-02-28 17:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:24 [PATCH] xen: add support for MSI message groups Roger Pau Monne
2014-02-27 12:42 ` David Vrabel
2014-02-27 12:42 ` [Xen-devel] " David Vrabel
2014-02-27 14:55 ` Boris Ostrovsky
2014-02-27 14:55 ` [Xen-devel] " Boris Ostrovsky
2014-02-27 15:45   ` Roger Pau Monné
2014-02-27 15:45   ` [Xen-devel] " Roger Pau Monné
2014-02-27 16:33     ` Boris Ostrovsky
2014-02-27 16:40       ` Roger Pau Monné
2014-02-27 16:40       ` [Xen-devel] " Roger Pau Monné
2014-02-27 18:15       ` [PATCH v2] " Roger Pau Monne
2014-02-27 18:45         ` Boris Ostrovsky
2014-02-28 17:20           ` Boris Ostrovsky
2014-02-28 17:20           ` Boris Ostrovsky
2014-02-28 17:46             ` Roger Pau Monné [this message]
2014-02-28 17:46             ` Roger Pau Monné
2014-02-28 18:00               ` Boris Ostrovsky
2014-02-28 18:00               ` Boris Ostrovsky
2014-02-28 18:10                 ` Roger Pau Monné
2014-02-28 18:10                 ` Roger Pau Monné
2014-02-28 18:36                   ` Boris Ostrovsky
2014-02-28 19:41                     ` David Vrabel
2014-02-28 19:41                     ` David Vrabel
2014-02-28 18:36                   ` Boris Ostrovsky
2014-02-27 18:45         ` Boris Ostrovsky
2014-02-27 18:15       ` Roger Pau Monne
2014-02-27 16:33     ` [PATCH] " Boris Ostrovsky

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='5310CB6F.1070706__25525.6242388443$1393609693$gmane$org@citrix.com' \
    --to=roger.pau@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xen.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.