From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Sumit Saxena <sumit.saxena@broadcom.com>,
"helgaas@kernel.org" <helgaas@kernel.org>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] PCI: set BAR size bits correctly in Resize BAR control register
Date: Sun, 21 Jul 2019 14:47:17 +0000 [thread overview]
Message-ID: <90cdfa16-5fdf-e9a4-4e5d-e4b7651f181b@amd.com> (raw)
In-Reply-To: <CAL2rwxpc-Ub7ufs1SEEmnNaxtZg2KtY-QAuQnu95kXVPN8Z02Q@mail.gmail.com>
Am 19.07.19 um 19:56 schrieb Sumit Saxena:
> +Christian Koenig
>
> On Tue, Jul 16, 2019 at 3:41 PM Sumit Saxena <sumit.saxena@broadcom.com> wrote:
>> In Resize BAR control register, bits[8:12] represents size of BAR.
>> As per PCIe specification, below is encoded values in register bits
>> to actual BAR size table:
>>
>> Bits BAR size
>> 0 1 MB
>> 1 2 MB
>> 2 4 MB
>> 3 8 MB
>> --
>>
>> For 1 MB BAR size, BAR size bits should be set to 0 but incorrectly
>> these bits are set to "1f".
>> Latest megaraid_sas and mpt3sas adapters which support Resizable BAR
>> with 1 MB BAR size fails to initialize during system resume from S3 sleep.
>>
>> Fix: Correctly set BAR size bits to "0" for 1MB BAR size.
>>
>> CC: stable@vger.kernel.org # v4.16+
>> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203939
>> Fixes: d3252ace0bc652a1a244455556b6a549f969bf99 ("PCI: Restore resized BAR state on resume")
>> Signed-off-by: Sumit Saxena <sumit.saxena@broadcom.com>
>> ---
>> drivers/pci/pci.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>> index 8abc843..b651f32 100644
>> --- a/drivers/pci/pci.c
>> +++ b/drivers/pci/pci.c
>> @@ -1417,12 +1417,13 @@ static void pci_restore_rebar_state(struct pci_dev *pdev)
>>
>> for (i = 0; i < nbars; i++, pos += 8) {
>> struct resource *res;
>> - int bar_idx, size;
>> + int bar_idx, size, order;
>>
>> pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL, &ctrl);
>> bar_idx = ctrl & PCI_REBAR_CTRL_BAR_IDX;
>> res = pdev->resource + bar_idx;
>> - size = order_base_2((resource_size(res) >> 20) | 1) - 1;
>> + order = order_base_2((resource_size(res) >> 20) | 1);
>> + size = order ? order - 1 : 0;
That actually doesn't looks like it is correct or at least it's
unnecessary complex.
The " >> 20) | 1" seems like a copy & paste error from the code in
amdgpu where the BAR needs to larger than the VRAM size (which is not a
power of two).
So just using "size = order_base_2(resource_size(res) >> 20);" should be
sufficient here.
Regards,
Christian.
>> ctrl &= ~PCI_REBAR_CTRL_BAR_SIZE;
>> ctrl |= size << PCI_REBAR_CTRL_BAR_SHIFT;
>> pci_write_config_dword(pdev, pos + PCI_REBAR_CTRL, ctrl);
>> --
>> 1.8.3.1
>>
next prev parent reply other threads:[~2019-07-21 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 18:09 [PATCH] PCI: set BAR size bits correctly in Resize BAR control register Sumit Saxena
2019-07-19 17:56 ` Sumit Saxena
2019-07-21 14:47 ` Koenig, Christian [this message]
2019-07-21 15:09 ` Sumit Saxena
-- strict thread matches above, loose matches on Subject: below --
2019-07-25 19:17 Sumit Saxena
2019-07-25 11:20 ` Sumit Saxena
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=90cdfa16-5fdf-e9a4-4e5d-e4b7651f181b@amd.com \
--to=christian.koenig@amd.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.saxena@broadcom.com \
/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.