From: Maximilian Luz <luzmaximilian@gmail.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: Dorian Stoll <dorian.stoll@tmsp.io>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Plans for i915 GuC Submission with regards to IPTS/ME
Date: Sat, 28 Dec 2019 13:24:59 +0100 [thread overview]
Message-ID: <f9df12be-b34b-19ed-d052-42731d2dbd7c@gmail.com> (raw)
In-Reply-To: <bc31eaa3-c5ed-819f-a94a-1f7ca335ea86@intel.com>
Hi,
On 12/23/19 7:55 PM, Daniele Ceraolo Spurio wrote:
> If you only care about gen9, a possible solution would be to
> forward-port just the old GuC submission (instead of the whole i915)
> from a know working kernel. It shouldn't be too bad since the GuC code
> is relatively self-contained, but given the speed at which our
> submission code evolves there might be issue in the interactions
> between the old GuC code and the other parts of the submission flow.
Right, we may have to look at that. We're currently looking into a
non-GuC workaround as there doesn't seem to be any OpenCL kernels for
the Surface Pro 7/Surface Laptop 3 devices (that's another issue...),
but we will keep that in mind for the older devices.
> No idea about the details of what goes on on Windows. The firmware is
> OS-agnostic, but they might be using a different version compared to
> us, especially on older platforms.
Yeah, I suspect they're using older firmware on the older devices. Just
wanted to know if there's any special stuff on Windows. Given that the
newer devices (Pro 7/Laptop 3) don't seem to have any IPTS firmware at
all (OpenCL kernels etc.) could suggest that they might use a different
implementation (maybe non-GuC/no GPU processing), altough the IPTS
driver still seems to be in use.
Thank you for sharing your insights, this has really helped us.
Regards,
Maximilian
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-12-29 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 11:12 [Intel-gfx] Plans for i915 GuC Submission with regards to IPTS/ME Maximilian Luz
2019-12-16 22:40 ` Daniele Ceraolo Spurio
[not found] ` <bc4e8a25-05b5-72fb-8ddd-2275b739f0a5@gmail.com>
2019-12-23 18:55 ` Daniele Ceraolo Spurio
2019-12-28 12:24 ` Maximilian Luz [this message]
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=f9df12be-b34b-19ed-d052-42731d2dbd7c@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dorian.stoll@tmsp.io \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.