From: Alex Deucher <alexdeucher@gmail.com>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Tao Zhou <tao.zhou1@amd.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel-build-reports@lists.linaro.org"
<kernel-build-reports@lists.linaro.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"alexander.deucher@amd.com" <alexander.deucher@amd.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"christian.koenig@amd.com" <christian.koenig@amd.com>,
"dennis.li@amd.com" <dennis.li@amd.com>,
"hawking.zhang@amd.com" <hawking.zhang@amd.com>
Subject: Re: [PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations
Date: Wed, 7 Aug 2019 00:02:35 -0400 [thread overview]
Message-ID: <CADnq5_O4SJexzU2V5+B8tBcTPDU6nR1LakaOMpNng5veOo4guw@mail.gmail.com> (raw)
In-Reply-To: <20190807105759.58a28ef0@xhacker.debian>
On Tue, Aug 6, 2019 at 11:31 PM Jisheng Zhang
<Jisheng.Zhang@synaptics.com> wrote:
>
> On Wed, 7 Aug 2019 10:56:40 +0800 Tao Zhou wrote:
>
>
> >
> >
> > readq/writeq are not supported on all architectures
> >
> > Signed-off-by: Tao Zhou <tao.zhou1@amd.com>
> > ---
> > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++------
> > 1 file changed, 2 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > index 558fe6d091ed..7eb9e0b9235a 100644
> > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> > @@ -272,14 +272,10 @@ void amdgpu_mm_wreg(struct amdgpu_device *adev, uint32_t reg, uint32_t v,
> > */
> > uint64_t amdgpu_mm_rreg64(struct amdgpu_device *adev, uint32_t reg)
> > {
> > - uint64_t ret;
> > -
> > if ((reg * 4) < adev->rmmio_size)
> > - ret = readq(((void __iomem *)adev->rmmio) + (reg * 4));
> > + return atomic64_read((atomic64_t *)(adev->rmmio + (reg * 4)));
>
> atomic64_read doesn't equal to readq on some architectures..
What we really wanted originally was atomic64. We basically want a
read or write that is guaranteed to be 64 bits at a time.
Alex
>
> > else
> > BUG();
> > -
> > - return ret;
> > }
> >
> > /**
> > @@ -294,7 +290,7 @@ uint64_t amdgpu_mm_rreg64(struct amdgpu_device *adev, uint32_t reg)
> > void amdgpu_mm_wreg64(struct amdgpu_device *adev, uint32_t reg, uint64_t v)
> > {
> > if ((reg * 4) < adev->rmmio_size)
> > - writeq(v, ((void __iomem *)adev->rmmio) + (reg * 4));
> > + atomic64_set((atomic64_t *)(adev->rmmio + (reg * 4)), v);
> > else
> > BUG();
> > }
> > --
> > 2.17.1
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2019-08-07 4:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 2:56 [PATCH] drm/amdgpu: replace readq/writeq with atomic64 operations Tao Zhou
2019-08-07 3:09 ` Jisheng Zhang
2019-08-07 4:02 ` Alex Deucher [this message]
2019-08-07 4:03 ` Alex Deucher
2019-08-07 7:08 ` Christoph Hellwig
2019-08-07 8:53 ` Koenig, Christian
2019-08-07 10:41 ` Christoph Hellwig
2019-08-07 10:55 ` Koenig, Christian
2019-08-07 12:59 ` Mark Brown
2019-08-07 13:00 ` Koenig, Christian
2019-08-07 13:07 ` Christoph Hellwig
2019-08-07 13:00 ` Christoph Hellwig
2019-08-07 13:03 ` Koenig, Christian
2019-08-07 18:00 ` Alex Deucher
2019-08-08 19:25 ` Guenter Roeck
2019-08-08 19:33 ` Alex Deucher
2019-08-09 9:04 ` Koenig, Christian
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=CADnq5_O4SJexzU2V5+B8tBcTPDU6nR1LakaOMpNng5veOo4guw@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=broonie@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dennis.li@amd.com \
--cc=hawking.zhang@amd.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=tao.zhou1@amd.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).