From: Andi Kleen <ak@linux.intel.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: rusty@rustcorp.com.au, Dana Elifaz <Dana.Elifaz@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Oded Gabbay <oded.gabbay@amd.com>,
Alexander Deucher <Alexander.Deucher@amd.com>,
LKP ML <lkp@01.org>
Subject: Re: [LKP] [PATCH] drm/radeon: Try to init amdkfd only if 64 bit kernel
Date: Mon, 22 Dec 2014 11:00:41 -0800 [thread overview]
Message-ID: <20141222190041.GC17192@tassilo.jf.intel.com> (raw)
In-Reply-To: <20141222184940.GB17192@tassilo.jf.intel.com>
On Mon, Dec 22, 2014 at 10:49:40AM -0800, Andi Kleen wrote:
> On Mon, Dec 22, 2014 at 11:58:43AM -0500, Alex Deucher wrote:
> > On Mon, Dec 22, 2014 at 6:11 AM, Oded Gabbay <oded.gabbay@amd.com> wrote:
> > > amdkfd driver can be compiled only in 64-bit kernel. Therefore, there is no
> > > point in trying to initialize amdkfd in 32-bit kernel.
> > >
> > > In addition, in case of specific configuration of 32-bit kernel, no modules and
> > > random kernel base, the symbol_request function doesn't work as expected - It
> > > doesn't return NULL if the symbol doesn't exists. That makes the kernel panic.
> > > Therefore, the as amdkfd doesn't compile in 32-bit kernel, the best way is just
> > > to return false immediately.
> > >
> > > Signed-off-by: Oded Gabbay <oded.gabbay@amd.com>
> >
> > Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
>
> Sorry but the patch is just bogus. X-bit only code is usually
> a very bad sign for the code. This is not windows programing after all.
>
> Even if you wanted to do a 64bit only driver -- which
> you probably don't -- the standard way would be to exclude
> it in Kconfig.
>
> Please root-cause why symbol_request doesn't work on 32bit
> and fix it properly.
>
> +rusty.
And also with correct email.
-Andi
next prev parent reply other threads:[~2014-12-22 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 11:11 [PATCH] drm/radeon: Try to init amdkfd only if 64 bit kernel Oded Gabbay
2014-12-22 16:58 ` Alex Deucher
2014-12-22 18:49 ` [LKP] " Andi Kleen
2014-12-22 19:00 ` Andi Kleen [this message]
2014-12-22 19:18 ` Oded Gabbay
2014-12-23 23:01 ` Rusty Russell
2014-12-24 9:22 ` Oded Gabbay
2015-01-05 4:28 ` Rusty Russell
2015-01-06 20:14 ` Kees Cook
2015-01-06 22:58 ` Rusty Russell
2015-01-11 11:57 ` Oded Gabbay
2015-01-13 17:15 ` Kees Cook
2015-01-16 0:27 ` Kees Cook
2015-01-16 11:27 ` Oded Gabbay
2015-01-23 4:10 ` Rusty Russell
2014-12-25 12:31 ` Christian König
2014-12-28 9:05 ` Oded Gabbay
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=20141222190041.GC17192@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=Alexander.Deucher@amd.com \
--cc=Dana.Elifaz@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=oded.gabbay@amd.com \
--cc=rusty@rustcorp.com.au \
/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).