From: Michael Ellerman <mpe@ellerman.id.au>
To: Wei Yang <weiyang@linux.vnet.ibm.com>,
gwshan@linux.vnet.ibm.com, aik@ozlabs.ru,
benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Wei Yang <weiyang@linux.vnet.ibm.com>
Subject: Re: [V7, 1/6] powerpc/powernv: don't enable SRIOV when VF BAR has non 64bit-prefetchable BAR
Date: Wed, 17 Feb 2016 23:41:27 +1100 (AEDT) [thread overview]
Message-ID: <20160217124127.26B1914032B@ozlabs.org> (raw)
In-Reply-To: <1445476939-2995-2-git-send-email-weiyang@linux.vnet.ibm.com>
On Thu, 2015-22-10 at 01:22:14 UTC, Wei Yang wrote:
> On PHB3, we enable SRIOV devices by mapping IOV BAR with M64 BARs. If a
> SRIOV device's IOV BAR is not 64bit-prefetchable, this is not assigned from
> 64bit prefetchable window, which means M64 BAR can't work on it.
>
> The reason is PCI bridges support only 2 memory windows and the kernel code
> programs bridges in the way that one window is 32bit-nonprefetchable and
> the other one is 64bit-prefetchable. So if devices' IOV BAR is 64bit and
> non-prefetchable, it will be mapped into 32bit space and therefore M64
> cannot be used for it.
>
> This patch makes this explicit and truncate IOV resource in this case to
> save MMIO space.
>
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> Reviewed-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
> Acked-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b0331854190e70b9d96d392572
cheers
next prev parent reply other threads:[~2016-02-17 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 1:22 [PATCH V7 0/6] Redesign SR-IOV on PowerNV Wei Yang
2015-10-22 1:22 ` [PATCH V7 1/6] powerpc/powernv: don't enable SRIOV when VF BAR has non 64bit-prefetchable BAR Wei Yang
2016-02-17 12:41 ` Michael Ellerman [this message]
2015-10-22 1:22 ` [PATCH V7 2/6] powerpc/powernv: simplify the calculation of iov resource alignment Wei Yang
2015-10-22 1:22 ` [PATCH V7 3/6] powerpc/powernv: use one M64 BAR in Single PE mode for one VF BAR Wei Yang
2015-10-22 1:22 ` [PATCH V7 4/6] powerpc/powernv: replace the hard coded boundary with gate Wei Yang
2015-10-22 1:22 ` [PATCH V7 5/6] powerpc/powernv: boundary the total VF BAR size instead of the individual one Wei Yang
2015-10-22 1:22 ` [PATCH V7 6/6] powerpc/powernv: allocate sparse PE# when using M64 BAR in Single PE mode Wei Yang
2015-10-22 11:13 ` [PATCH V7 0/6] Redesign SR-IOV on PowerNV Gavin Shan
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=20160217124127.26B1914032B@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=weiyang@linux.vnet.ibm.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 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).