linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"mj@ucw.cz" <mj@ucw.cz>
Subject: Re: [PATCH] Fix Vector table and PBA addresses print output
Date: Tue, 30 Jan 2018 16:08:07 +0000	[thread overview]
Message-ID: <80372960-864f-0f7d-db04-c2cb49631f63@synopsys.com> (raw)
In-Reply-To: <20180130070718.335deb52@w520.home>

Hi Alex,

On 30/01/2018 14:07, Alex Williamson wrote:
> On Tue, 30 Jan 2018 10:34:08 +0000
> Gustavo Pimentel <gustavo.pimentel@synopsys.com> wrote:
> 
>> Lack of 3-bit rotation to the right was leading to erroneous display of the
>> vector table and PBA.
>>
>> Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
>> ---
>>  ls-caps.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/ls-caps.c b/ls-caps.c
>> index 507771a..cd13a37 100644
>> --- a/ls-caps.c
>> +++ b/ls-caps.c
>> @@ -1104,10 +1104,10 @@ cap_msix(struct device *d, int where, int cap)
>>  
>>    off = get_conf_long(d, where + PCI_MSIX_TABLE);
>>    printf("\t\tVector table: BAR=%d offset=%08x\n",
>> -	 off & PCI_MSIX_BIR, off & ~PCI_MSIX_BIR);
>> +	 off & PCI_MSIX_BIR, (off & ~PCI_MSIX_BIR) >> 3);
>>    off = get_conf_long(d, where + PCI_MSIX_PBA);
>>    printf("\t\tPBA: BAR=%d offset=%08x\n",
>> -	 off & PCI_MSIX_BIR, off & ~PCI_MSIX_BIR);
>> +	 off & PCI_MSIX_BIR, (off & ~PCI_MSIX_BIR) >> 3);
>>  }
>>  
>>  static void
> 
> 
> The code is correct as is, the register contains bits 31:3 of the
> offset.  The spec states (PCI rev 3.0, 6.8.2.4, 6.8.2.5):

I have just downloaded now the rev 3.0 (PCI_Express_Base_r3.0_10Nov10.pdf,
November 10, 2010) from PCI-SIG and the chapters that you refer don't match with
the downloaded version, can you confirm the doc date?

> 
>   The lower 3 Table BIR bits are masked off (set to zero) by software
>   to form a 32-bit QWORD -aligned offset.
> 
>   The lower 3 PBA BIR bits are masked off (set to zero) by software to
>   form a 32-bit QWORD-aligned offset.
>

Yes, I understand the meaning but for the user the value printed should not
include (in my perspective) the offset provide by the Table BIR field or the PBA
BIR field.

> Shifting is incorrect, the mask operation fills the lower 3 bits.
The spec defines:
       | 31         24 | 23         16 | 15         8 | 7        3 | 2     0 |
  +00h |           Msg Ctrl Reg        |    PNext ID  |       CapID          |
  +04h |                        Table offset                       | Tb BIR  |
  +08h |                        PBA offset                         | PBA BIR |
  +0Ch |            Reserved           |         Msg Data Reg                |

Let's apply a real example here, using the info from config space:
       | 31         24 | 23         16 | 15         8 | 7                  0 |
0b+00h |      00       |      20       |      00      |         11           |
0b+04h |      00       |      00       |      00      |         00           |
0b+08h |      00       |      00       |      18      |         00           |
0b+0Ch |      00       |      00       |      00      |         00           |

If I decode manually the info from config space, I get for each field the
following value:

Msg Ctrl Reg = 0x20
PNext ID = 0x0
CapID = 0x11
Table offset = 0x0
Table BIR = 0x0
Table offset = 0x300
Table BIR = 0x0
Msg Data Reg = 0x0

Using lspci, I get:
...
    Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
        Vector table: BAR=0 offset=00000000
        PBA: BAR=0 offset=00001800
...
In my perspective should be like:

    Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
        Vector table: BAR=0 offset=00000000
        PBA: BAR=0 offset=00000300

> Thanks,
> 
> Alex
> 

Regards,
Gustavo

  reply	other threads:[~2018-01-30 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 10:34 [PATCH] Fix Vector table and PBA addresses print output Gustavo Pimentel
2018-01-30 14:07 ` Alex Williamson
2018-01-30 16:08   ` Gustavo Pimentel [this message]
2018-01-30 16:45     ` Alex Williamson
2018-01-31 12:41       ` Martin Mares

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=80372960-864f-0f7d-db04-c2cb49631f63@synopsys.com \
    --to=gustavo.pimentel@synopsys.com \
    --cc=alex.williamson@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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).