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: <linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH] xen: add support for MSI message groups
Date: Thu, 27 Feb 2014 17:40:54 +0100	[thread overview]
Message-ID: <530F6A96.2030508@citrix.com> (raw)
In-Reply-To: <530F68BE.2070505@oracle.com>

On 27/02/14 17:33, Boris Ostrovsky wrote:
> On 02/27/2014 10:45 AM, Roger Pau Monné wrote:
>>>
>>> @@ -291,7 +290,10 @@ static int xen_initdom_setup_msi_irqs(struct
>>> pci_dev *dev, int nvec, int type)
>>>                      (pci_domain_nr(dev->bus) << 16);
>>>            map_irq.devfn = dev->devfn;
>>>    -        if (type == PCI_CAP_ID_MSIX) {
>>> +        if (type == PCI_CAP_ID_MSI && nvec > 1) {
>>> +            map_irq.type = MAP_PIRQ_TYPE_MULTI_MSI;
>>> +            map_irq.entry_nr = nvec;
>>>
>>> Are we overloading entry_nr here with a different meaning? I thought it
>>> was meant to be entry number (in MSI-X table for example), not number of
>>> entries.
>> In the case of MSI message groups (MAP_PIRQ_TYPE_MULTI_MSI) entry_nr is
>> the number of vectors to setup, so yes, it's an overloading of entry_nr.
> 
> Then I think we should at least make a note of this in physdev.h. (Or
> maybe even make entry_nr a union with nvec or some such, although that
> would look rather hacky).

OK, I can add a comment to that effect in physdev.h.

> 
>> ....
>>
>>>
>>> index 42721d1..eb13326d 100644
>>> --- a/include/xen/interface/physdev.h
>>> +++ b/include/xen/interface/physdev.h
>>> @@ -131,6 +131,7 @@ struct physdev_irq {
>>>    #define MAP_PIRQ_TYPE_GSI        0x1
>>>    #define MAP_PIRQ_TYPE_UNKNOWN        0x2
>>>    #define MAP_PIRQ_TYPE_MSI_SEG        0x3
>>> +#define MAP_PIRQ_TYPE_MULTI_MSI        0x4
>>> Formatting.
>> I don't get the formatting problem, it's the same formatting that the
>> other MAP_PIRQ_TYPE_* use, and if the patch is applied formatting is OK.
>>
> 
> That's because my client messed up whitespaces. You can look for example
> at https://lkml.org/lkml/2014/2/26/352 to see the extra tab.

It looks like an extra tab because there's a "+" in front of the line,
which makes the tab jump. If you remove the extra "+" and the spaces in
front of the preceding lines it is going to be aligned.

Roger.

  parent reply	other threads:[~2014-02-27 16:40 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 ` [Xen-devel] " David Vrabel
2014-02-27 12:42 ` David Vrabel
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       ` Roger Pau Monné [this message]
2014-02-27 18:15       ` [PATCH v2] " Roger Pau Monne
2014-02-27 18:15       ` Roger Pau Monne
2014-02-27 18:45         ` Boris Ostrovsky
2014-02-27 18:45         ` Boris Ostrovsky
2014-02-28 17:20           ` Boris Ostrovsky
2014-02-28 17:46             ` Roger Pau Monné
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: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-28 18:10                 ` Roger Pau Monné
2014-02-28 17:20           ` Boris Ostrovsky
2014-02-27 16:33     ` [PATCH] " Boris Ostrovsky
2014-02-27 14:55 ` 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=530F6A96.2030508@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=boris.ostrovsky@oracle.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.