All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Gabriel C <nix.or.die@gmail.com>
Cc: "Christian König" <christian.koenig@amd.com>,
	"Christoph Hellwig" <hch@lst.de>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Jean-Marc Valin" <jmvalin@mozilla.com>,
	"Dave Airlie" <airlied@linux.ie>,
	"Felix Kuehling" <Felix.Kuehling@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org, "Joerg Roedel" <jroedel@suse.de>,
	alexander.deucher@amd.com,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Michel Dänzer" <michel@daenzer.net>
Subject: Re: Kernel and ADM hardware roulette ( was AMD graphics performance regression in 4.15 and later )
Date: Mon, 11 Jun 2018 09:15:01 +0200	[thread overview]
Message-ID: <20180611071501.GA1015@lst.de> (raw)
In-Reply-To: <CAEJqkggkZynDvV8XxkFfy89x-DX5xDTyubUJ3oXBO6eUjBWBKw@mail.gmail.com>

I think the prime issue is that dma_direct_alloc respects the dma
mask.  Which we don't need if actually using the iommu.  This would
be mostly harmless exept for the the SEV bit high in the address that
makes the checks fail.

For now I'd say revert this commit for 4.17/4.18-rc and I'll look into
addressing these issues properly.

  reply	other threads:[~2018-06-11  7:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 13:33 Kernel and ADM hardware roulette ( was AMD graphics performance regression in 4.15 and later ) Gabriel C
2018-06-06 14:12 ` Michel Dänzer
2018-06-06 14:12   ` Michel Dänzer
2018-06-06 14:44   ` Christian König
2018-06-06 14:44     ` Christian König
2018-06-06 15:03     ` Michel Dänzer
2018-06-06 15:03       ` Michel Dänzer
2018-06-06 15:44       ` Gabriel C
2018-06-07  7:07         ` Christian König
2018-06-07 12:32           ` Gabriel C
2018-06-07 16:24             ` Gabriel C
2018-06-07 17:20               ` Christian König
2018-06-08  6:01                 ` Christoph Hellwig
2018-06-08  6:47                   ` Christian König
2018-06-08  6:02             ` Christoph Hellwig
2018-06-08  6:02               ` Christoph Hellwig
2018-06-08  6:52               ` Christian König
2018-06-08  6:52                 ` Christian König
2018-06-08 13:32                 ` Gabriel C
2018-06-11  7:15                   ` Christoph Hellwig [this message]
2018-06-11 19:23                     ` Linus Torvalds
2018-06-11 19:23                       ` Linus Torvalds
2018-06-06 15:24     ` Gabriel C
2018-06-06 14:29 ` Christian König
2018-06-06 14:29   ` Christian König

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=20180611071501.GA1015@lst.de \
    --to=hch@lst.de \
    --cc=Felix.Kuehling@amd.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jmvalin@mozilla.com \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michel@daenzer.net \
    --cc=nix.or.die@gmail.com \
    --cc=thomas.lendacky@amd.com \
    --cc=torvalds@linux-foundation.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.