On Fri, Nov 02, 2018 at 09:47:11AM -0500, Jason Ekstrand wrote:
> On Fri, Nov 2, 2018 at 6:05 AM Toni Lönnberg
> wrote:
>
> > On Fri, Nov 02, 2018 at 12:09:54AM -0500, Jason Ekstrand wrote:
> > > On Thu, Nov 1, 2018 at 5:51 AM Toni Lönnberg
> > > wrote:
> > >
> > > > On Wed, Oct 31, 2018 at
On Fri, Nov 2, 2018 at 6:05 AM Toni Lönnberg
wrote:
> On Fri, Nov 02, 2018 at 12:09:54AM -0500, Jason Ekstrand wrote:
> > On Thu, Nov 1, 2018 at 5:51 AM Toni Lönnberg
> > wrote:
> >
> > > On Wed, Oct 31, 2018 at 01:18:11PM -0500, Jason Ekstrand wrote:
> > > > On Wed, Oct 31, 2018 at 11:10 AM
On Fri, Nov 02, 2018 at 12:09:54AM -0500, Jason Ekstrand wrote:
> On Thu, Nov 1, 2018 at 5:51 AM Toni Lönnberg
> wrote:
>
> > On Wed, Oct 31, 2018 at 01:18:11PM -0500, Jason Ekstrand wrote:
> > > On Wed, Oct 31, 2018 at 11:10 AM Toni Lönnberg
> > > wrote:
> > >
> > > > When we debug media or
On Thu, Nov 1, 2018 at 5:51 AM Toni Lönnberg
wrote:
> On Wed, Oct 31, 2018 at 01:18:11PM -0500, Jason Ekstrand wrote:
> > On Wed, Oct 31, 2018 at 11:10 AM Toni Lönnberg
> > wrote:
> >
> > > When we debug media or 3d+media workloads, we'd like to be able to see
> > > what is
> > > in the aub
On Wed, Oct 31, 2018 at 01:18:11PM -0500, Jason Ekstrand wrote:
> On Wed, Oct 31, 2018 at 11:10 AM Toni Lönnberg
> wrote:
>
> > When we debug media or 3d+media workloads, we'd like to be able to see
> > what is
> > in the aub dumps for those workloads. At the moment the decoder can't
> >
On Wed, Oct 31, 2018 at 9:34 AM Lionel Landwerlin <
lionel.g.landwer...@intel.com> wrote:
> On 31/10/2018 14:20, Jason Ekstrand wrote:
>
> Toni,
>
> I'm a bit curious where you're going with this. I started on a similar
> project a couple of years ago:
>
>
On Wed, Oct 31, 2018 at 11:10 AM Toni Lönnberg
wrote:
> When we debug media or 3d+media workloads, we'd like to be able to see
> what is
> in the aub dumps for those workloads. At the moment the decoder can't
> distinguish instructions which share the same opcode between the render
> and
> video
When we debug media or 3d+media workloads, we'd like to be able to see what is
in the aub dumps for those workloads. At the moment the decoder can't
distinguish instructions which share the same opcode between the render and
video pipe, and thus aubinator outputs garbage on media instructions.
On 31/10/2018 14:20, Jason Ekstrand wrote:
Toni,
I'm a bit curious where you're going with this. I started on a
similar project a couple of years ago:
https://gitlab.freedesktop.org/jekstrand/mesa/commits/wip/genxml-engines
Mine took a different (not necessarily better) approach of
Toni,
I'm a bit curious where you're going with this. I started on a similar
project a couple of years ago:
https://gitlab.freedesktop.org/jekstrand/mesa/commits/wip/genxml-engines
Mine took a different (not necessarily better) approach of surrounding the
instructions in an tag. I'm not sure
These patches add an engine parameter to the instructions defined in the genxml
files so that they can be distinguished when sending them to different engines.
By default, an instruction is defined to be used by all engines and is defined
for a specific engine by adding the parameter "engine" to
11 matches
Mail list logo
