From: "Zhigang Gong" <zhigang.gong@linux.intel.com>
To: 'Andi Kleen' <andi@firstfloor.org>, daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, beignet@lists.freedesktop.org
Subject: Re: Haswell issues
Date: Thu, 30 Apr 2015 13:49:31 +0800 [thread overview]
Message-ID: <00b901d08309$6f59ba00$4e0d2e00$@linux.intel.com> (raw)
In-Reply-To: <871tj2nt95.fsf@tassilo.jf.intel.com>
Andi,
Thanks for your comments and that makes sense for me, just check kernel version is not
an ideal method for those unofficial kernels with back porting patches. Then we have the
following open questions in my mind:
How do we check whether the i915 KMD support secure batch buffer execution if the batch
buffer pass the cmd parser check under full-ppgtt mode in UMD?
How do we check whether the i915 KMD support secure batch buffer execution with aliasing
ppgtt after the merging of the patch "drm/i915: Arm cmd parser with aliasing ppgtt only" in UMD?
CC to Daniel, do you have any suggestion here?
Thanks,
Zhigang Gong.
> -----Original Message-----
> From: Beignet [mailto:beignet-bounces@lists.freedesktop.org] On Behalf Of
> Andi Kleen
> Sent: Thursday, April 30, 2015 12:19 PM
> To: beignet@lists.freedesktop.org
> Cc: zhigang.gong@linux.intel.com
> Subject: Re: [Beignet] Haswell issues
>
> "Zhigang Gong" <zhigang.gong@linux.intel.com> writes:
> >> but I don't have the hardware to try it.
> > We will do some testing on this. And once we get the exact version, I
> > will submit a new patch to give some warn if the user is using an
> > unsupported kernel. As now we have better solution than patch kernel
> > manually, I will change the document to suggest user to upgrade to a
> supported kernel rather than patch kernel manually.
>
> It would be better to add something to the kernel interface that can be probed
> without relying on the kernel version. The problem with checking versions is
> that it'll break if someone backports the fixes to older kernels, which is not
> uncommon.
>
> -Andi
>
> --
> ak@linux.intel.com -- Speaking for myself only
>
> _______________________________________________
> Beignet mailing list
> Beignet@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/beignet
_______________________________________________
Beignet mailing list
Beignet@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/beignet
parent reply other threads:[~2015-04-30 5:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <871tj2nt95.fsf@tassilo.jf.intel.com>]
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='00b901d08309$6f59ba00$4e0d2e00$@linux.intel.com' \
--to=zhigang.gong@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=beignet@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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