From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 83708] [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address Date: Thu, 25 Sep 2014 02:18:31 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1015233756==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2C1616E6B5 for ; Wed, 24 Sep 2014 19:18:31 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1015233756== Content-Type: multipart/alternative; boundary="1411611511.c25AFE700.525"; charset="us-ascii" --1411611511.c25AFE700.525 Date: Thu, 25 Sep 2014 02:18:31 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D83708 --- Comment #16 from Michel D=C3=A4nzer --- (In reply to comment #15) > 1. I do not add cpu_to_le32() first ,but when I trace the messages from > printk,the value of msg_type is reversed. That's in radeon_uvd_cs_msg()? Sounds like the Mesa UVD code writes the messages in host byte order, not in little endian. Maybe Christian can clar= ify which byte order should be used for them. > 2. #if 0 ...#endif is the original code from kernel. #if 1 ...#endif is > changed code. Ah right, never mind, I misread that hunk before. > By the way, u said writel() and readl() already convert to/from little > endian. is based on the X86 arch implement? It's the same on all architectures: writel() takes a datum in host byte ord= er and writes it in little endian. readl() reads a little endian datum and ret= urns it in host byte order. (This means that on little endian hosts such as x86,= the datum is transferred unchanged) --=20 You are receiving this mail because: You are the assignee for the bug. --1411611511.c25AFE700.525 Date: Thu, 25 Sep 2014 02:18:31 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 16 on bug 83708<= /a> from Michel D=C3=A4nzer
(In reply to comment #=
15)
> 1. I do not add cpu_to_le32() first ,but when I =
trace the messages from
> printk,the value of msg_type is reversed.

That's in radeon_uvd_cs_msg()? Sounds like the Mesa UVD code writes the
messages in host byte order, not in little endian. Maybe Christian can clar=
ify
which byte order should be used for them.


> 2. #if 0 ...#endif is the original code from ker=
nel. #if 1 ...#endif is
> changed code.

Ah right, never mind, I misread that hunk before.


> By the way, u said writel() and readl() already =
convert to/from little
> endian. is based on the X86 arch implement?

It's the same on all architectures: writel() takes a datum in host byte ord=
er
and writes it in little endian. readl() reads a little endian datum and ret=
urns
it in host byte order. (This means that on little endian hosts such as x86,=
 the
datum is transferred unchanged)


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1411611511.c25AFE700.525-- --===============1015233756== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1015233756==--