From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] ltp_tpci.c: Add release operation before allocation
Date: Mon, 26 Jul 2021 10:36:51 +0200 [thread overview]
Message-ID: <YP50I9N3dfASNrvz@pevik> (raw)
In-Reply-To: <ca6ecb17-c1b4-0d8a-a3c4-dc5e8e2bd275@canonical.com>
Hi all,
> On 07/07/2021 09:04, Krzysztof Kozlowski wrote:
> > On 29/06/2021 11:38, Krzysztof Kozlowski wrote:
> >> On 28/06/2021 22:29, Petr Vorel wrote:
> >>> Hi Xin,
> >>>> When we run the test case, the following results will be obtained:
> >>>> test_pci 283 TPASS : PCI bus 7d slot 00 : Test-case '11'
> >>>> test_pci 284 TFAIL : tpci.c:74: PCI bus 7d slot 00 : Test-case '12'
> >>>> ...
> >>>> test_pci 300 TFAIL : tpci.c:74: PCI bus 7d slot 01 : Test-case '12'
> >>>> test_pci 301 TPASS : PCI bus 7d slot 01 : Test-case '13'
> >>>> The analysis is that the space allocated by the bios is insufficient.
> >>>> The solution to this problem can be in add pci_release_resource(dev, i)
> >>>> before system resources are reallocated.Because the resources have been
> >>>> allocated when the system is initialized.If it is redistributed, it
> >>>> should be released and then allocated.
> >>> I wonder if this is the same issue as the one described by Krzysztof in his
> >>> patch:
> >>> https://patchwork.ozlabs.org/project/ltp/patch/20210401125127.45600-1-wangxin410@huawei.com/
> >>> Could you please share what HW and kernel you use and post dmesg?
> >> This solves my problem. It seems that could be the root cause - early
> >> configuration allocated too small resource? It might be also some
> >> specific BIOS issue (wrong resource allocated?) because in case of
> >> resource assignment failure, the kernel should try to get the original
> >> FW address from BIOS (pcibios_retrieve_fw_addr()) and this apparently
> >> returns NULL translated to -ENOMEM.
> >> I am fine with going with this patch instead of mine.
> > Is there anything stopping Xin's patch from being applied? LGTM:
Lack of time :)
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Oh, I see what's wrong with the patch - it's corrupted, not possible to
> apply.
Trivial fix, I'll merge it shortly.
Kind regards,
Petr
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2021-07-26 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:51 [LTP] [PATCH] ltp_tpci.c: Add release operation before allocation Wang Xin
2021-06-28 20:29 ` Petr Vorel
2021-06-29 9:38 ` Krzysztof Kozlowski
2021-07-07 7:04 ` Krzysztof Kozlowski
2021-07-07 7:21 ` Krzysztof Kozlowski
2021-07-26 8:36 ` Petr Vorel [this message]
2021-07-26 8:40 ` Petr Vorel
2021-07-26 8:44 ` Krzysztof Kozlowski
2021-07-26 8:55 ` Petr Vorel
2021-06-30 2:14 ` [LTP] 答复: " wangxin
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=YP50I9N3dfASNrvz@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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