From: Alan Mikhak <alan.mikhak@sifive.com> To: Kishon Vijay Abraham I <kishon@ti.com> Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, lorenzo.pieralisi@arm.com, linux-riscv@lists.infradead.org, Palmer Dabbelt <palmer@sifive.com>, Paul Walmsley <paul.walmsley@sifive.com>, Bjorn Helgaas <bhelgaas@google.com>, Gustavo Pimentel <gustavo.pimentel@synopsys.com>, wen.yang99@zte.com.cn, kjlu@umn.edu Subject: Re: [PATCH v2] PCI: endpoint: Skip odd BAR when skipping 64bit BAR Date: Fri, 31 May 2019 09:52:31 -0700 [thread overview] Message-ID: <CABEDWGyQHh=8fmZFAK6acecDSF_-pfpa9NCZOQ--WDhZiZPihw@mail.gmail.com> (raw) In-Reply-To: <96365941-512b-dfb2-05b7-0780e8961f6c@ti.com> On Thu, May 30, 2019 at 9:37 PM Kishon Vijay Abraham I <kishon@ti.com> wrote: > > Hi Alan, > > On 25/05/19 12:20 AM, Alan Mikhak wrote: > > Hi Kishon, > > > > Yes. This change is still applicable even when the platform specifies > > that it only supports 64-bit BARs by setting the bar_fixed_64bit > > member of epc_features. > > > > The issue being fixed is this: If the 'continue' statement is executed > > within the loop, the loop index 'bar' needs to advanced by two, not > > one, when the BAR is 64-bit. Otherwise the next loop iteration will be > > on an odd BAR which doesn't exist. > > IIUC you are fixing the case where the BAR is "reserved" (specified in > epc_features) and is also a 64-bit BAR? Correct. If BAR0 is specified in epc_features as reserved and also 64-bit, the loop would skip BAR0 by executing the 'continue' statement. In this scenario, BAR1 doesn't exist since the 64-bit BAR0 spans the two 32-bit BAR0 and BAR1. The loop index 'bar' would be advanced by 2 in this case so on the next iteration the loop would process BAR2. > If 2 consecutive BARs are marked as reserved in reserved_bar of epc_features, > the result should be the same right? If both BAR0 and BAR2 are reserved and also 64-bit, the loop would check BAR0 on its first iteration and skip BAR0 and BAR1, check BAR2 on its second iteration and skip BAR2 and BAR3, then check BAR4 on its third iteration. If BAR4 is also 64-bit and reserved, the loop would skip BAR4 and BAR5 and that would be the final iteration of the loop. Regards, Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Mikhak <alan.mikhak@sifive.com> To: Kishon Vijay Abraham I <kishon@ti.com> Cc: lorenzo.pieralisi@arm.com, linux-pci@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>, kjlu@umn.edu, linux-kernel@vger.kernel.org, Paul Walmsley <paul.walmsley@sifive.com>, Bjorn Helgaas <bhelgaas@google.com>, linux-riscv@lists.infradead.org, Gustavo Pimentel <gustavo.pimentel@synopsys.com>, wen.yang99@zte.com.cn Subject: Re: [PATCH v2] PCI: endpoint: Skip odd BAR when skipping 64bit BAR Date: Fri, 31 May 2019 09:52:31 -0700 [thread overview] Message-ID: <CABEDWGyQHh=8fmZFAK6acecDSF_-pfpa9NCZOQ--WDhZiZPihw@mail.gmail.com> (raw) In-Reply-To: <96365941-512b-dfb2-05b7-0780e8961f6c@ti.com> On Thu, May 30, 2019 at 9:37 PM Kishon Vijay Abraham I <kishon@ti.com> wrote: > > Hi Alan, > > On 25/05/19 12:20 AM, Alan Mikhak wrote: > > Hi Kishon, > > > > Yes. This change is still applicable even when the platform specifies > > that it only supports 64-bit BARs by setting the bar_fixed_64bit > > member of epc_features. > > > > The issue being fixed is this: If the 'continue' statement is executed > > within the loop, the loop index 'bar' needs to advanced by two, not > > one, when the BAR is 64-bit. Otherwise the next loop iteration will be > > on an odd BAR which doesn't exist. > > IIUC you are fixing the case where the BAR is "reserved" (specified in > epc_features) and is also a 64-bit BAR? Correct. If BAR0 is specified in epc_features as reserved and also 64-bit, the loop would skip BAR0 by executing the 'continue' statement. In this scenario, BAR1 doesn't exist since the 64-bit BAR0 spans the two 32-bit BAR0 and BAR1. The loop index 'bar' would be advanced by 2 in this case so on the next iteration the loop would process BAR2. > If 2 consecutive BARs are marked as reserved in reserved_bar of epc_features, > the result should be the same right? If both BAR0 and BAR2 are reserved and also 64-bit, the loop would check BAR0 on its first iteration and skip BAR0 and BAR1, check BAR2 on its second iteration and skip BAR2 and BAR3, then check BAR4 on its third iteration. If BAR4 is also 64-bit and reserved, the loop would skip BAR4 and BAR5 and that would be the final iteration of the loop. Regards, Alan _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-31 16:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-23 21:55 [PATCH v2] PCI: endpoint: Skip odd BAR when skipping 64bit BAR Alan Mikhak 2019-05-23 21:55 ` Alan Mikhak 2019-05-23 23:55 ` Alan Mikhak 2019-05-23 23:55 ` Alan Mikhak 2019-05-24 8:49 ` Kishon Vijay Abraham I 2019-05-24 8:49 ` Kishon Vijay Abraham I 2019-05-24 18:50 ` Alan Mikhak 2019-05-24 18:50 ` Alan Mikhak 2019-05-30 16:22 ` Lorenzo Pieralisi 2019-05-30 16:22 ` Lorenzo Pieralisi 2019-05-31 4:35 ` Kishon Vijay Abraham I 2019-05-31 4:35 ` Kishon Vijay Abraham I 2019-05-31 16:52 ` Alan Mikhak [this message] 2019-05-31 16:52 ` Alan Mikhak 2019-05-24 8:49 ` Kishon Vijay Abraham I 2019-05-24 8:49 ` Kishon Vijay Abraham I 2019-06-03 7:34 ` Kishon Vijay Abraham I 2019-06-03 7:34 ` Kishon Vijay Abraham I 2019-06-11 10:08 ` Lorenzo Pieralisi 2019-06-11 10:08 ` Lorenzo Pieralisi
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='CABEDWGyQHh=8fmZFAK6acecDSF_-pfpa9NCZOQ--WDhZiZPihw@mail.gmail.com' \ --to=alan.mikhak@sifive.com \ --cc=bhelgaas@google.com \ --cc=gustavo.pimentel@synopsys.com \ --cc=kishon@ti.com \ --cc=kjlu@umn.edu \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=lorenzo.pieralisi@arm.com \ --cc=palmer@sifive.com \ --cc=paul.walmsley@sifive.com \ --cc=wen.yang99@zte.com.cn \ /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: linkBe 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.