From: "Koenig, Christian" <Christian.Koenig@amd.com>
To: Christoph Hellwig <hch@lst.de>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>
Cc: Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <alistair.francis@wdc.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] drm/radeon: handle PCIe root ports with addressing limitations
Date: Thu, 15 Aug 2019 08:34:10 +0000 [thread overview]
Message-ID: <d1cf1435-92e3-edb5-c239-18c71f2d27c7@amd.com> (raw)
In-Reply-To: <20190815072703.7010-2-hch@lst.de>
Am 15.08.19 um 09:27 schrieb Christoph Hellwig:
> radeon uses a need_dma32 flag to indicate to the drm core that some
> allocations need to be done using GFP_DMA32, but it only checks the
> device addressing capabilities to make that decision. Unfortunately
> PCIe root ports that have limited addressing exist as well. Use the
> dma_addressing_limited instead to also take those into account.
>
> Reported-by: Atish Patra <Atish.Patra@wdc.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks sane to me. Reviewed-by: Christian König <christian.koenig@amd.com>.
Should we merge this through our normal amdgpu/radeon branches or do you
want to send this upstream somehow else?
Thanks,
Christian.
> ---
> drivers/gpu/drm/radeon/radeon.h | 1 -
> drivers/gpu/drm/radeon/radeon_device.c | 12 +++++-------
> drivers/gpu/drm/radeon/radeon_ttm.c | 2 +-
> 3 files changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon.h b/drivers/gpu/drm/radeon/radeon.h
> index 32808e50be12..1a0b22526a75 100644
> --- a/drivers/gpu/drm/radeon/radeon.h
> +++ b/drivers/gpu/drm/radeon/radeon.h
> @@ -2387,7 +2387,6 @@ struct radeon_device {
> struct radeon_wb wb;
> struct radeon_dummy_page dummy_page;
> bool shutdown;
> - bool need_dma32;
> bool need_swiotlb;
> bool accel_working;
> bool fastfb_working; /* IGP feature*/
> diff --git a/drivers/gpu/drm/radeon/radeon_device.c b/drivers/gpu/drm/radeon/radeon_device.c
> index dceb554e5674..b8cc05826667 100644
> --- a/drivers/gpu/drm/radeon/radeon_device.c
> +++ b/drivers/gpu/drm/radeon/radeon_device.c
> @@ -1365,27 +1365,25 @@ int radeon_device_init(struct radeon_device *rdev,
> else
> rdev->mc.mc_mask = 0xffffffffULL; /* 32 bit MC */
>
> - /* set DMA mask + need_dma32 flags.
> + /* set DMA mask.
> * PCIE - can handle 40-bits.
> * IGP - can handle 40-bits
> * AGP - generally dma32 is safest
> * PCI - dma32 for legacy pci gart, 40 bits on newer asics
> */
> - rdev->need_dma32 = false;
> + dma_bits = 40;
> if (rdev->flags & RADEON_IS_AGP)
> - rdev->need_dma32 = true;
> + dma_bits = 32;
> if ((rdev->flags & RADEON_IS_PCI) &&
> (rdev->family <= CHIP_RS740))
> - rdev->need_dma32 = true;
> + dma_bits = 32;
> #ifdef CONFIG_PPC64
> if (rdev->family == CHIP_CEDAR)
> - rdev->need_dma32 = true;
> + dma_bits = 32;
> #endif
>
> - dma_bits = rdev->need_dma32 ? 32 : 40;
> r = pci_set_dma_mask(rdev->pdev, DMA_BIT_MASK(dma_bits));
> if (r) {
> - rdev->need_dma32 = true;
> dma_bits = 32;
> pr_warn("radeon: No suitable DMA available\n");
> }
> diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c
> index fb3696bc616d..116a27b25dc4 100644
> --- a/drivers/gpu/drm/radeon/radeon_ttm.c
> +++ b/drivers/gpu/drm/radeon/radeon_ttm.c
> @@ -794,7 +794,7 @@ int radeon_ttm_init(struct radeon_device *rdev)
> r = ttm_bo_device_init(&rdev->mman.bdev,
> &radeon_bo_driver,
> rdev->ddev->anon_inode->i_mapping,
> - rdev->need_dma32);
> + dma_addressing_limited(&rdev->pdev->dev));
> if (r) {
> DRM_ERROR("failed initializing buffer object driver(%d).\n", r);
> return r;
next prev parent reply other threads:[~2019-08-15 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 7:26 fix radeon and amdgpu for addressing limited root ports Christoph Hellwig
2019-08-15 7:27 ` [PATCH 1/4] drm/radeon: handle PCIe root ports with addressing limitations Christoph Hellwig
2019-08-15 8:34 ` Koenig, Christian [this message]
2019-08-15 10:06 ` Christoph Hellwig
2019-08-15 14:15 ` Alex Deucher
2019-08-15 14:29 ` Koenig, Christian
2019-08-15 7:27 ` [PATCH 2/4] drm/amdgpu: " Christoph Hellwig
2019-08-15 7:27 ` [PATCH 3/4] drm/radeon: simplify and cleanup setting the dma mask Christoph Hellwig
2019-08-15 7:27 ` [PATCH 4/4] drm/amdgpu: " Christoph Hellwig
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=d1cf1435-92e3-edb5-c239-18c71f2d27c7@amd.com \
--to=christian.koenig@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Atish.Patra@wdc.com \
--cc=David1.Zhou@amd.com \
--cc=alistair.francis@wdc.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®