All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>,
	"Alex Deucher" <alexander.deucher@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu/gmc: use PCI BARs for APUs in passthrough
Date: Fri, 11 Mar 2022 11:32:15 +0100	[thread overview]
Message-ID: <541dc1eb-cf50-17d2-0ae3-5c3cb3dc3ac0@gmail.com> (raw)
In-Reply-To: <ed66fa3d-51c8-1cd1-8709-30f66eb82fd3@mailbox.org>

Am 11.03.22 um 11:24 schrieb Michel Dänzer:
> On 2022-03-10 19:06, Alex Deucher wrote:
>> If the GPU is passed through to a guest VM, use the PCI
>> BAR for CPU FB access rather than the physical address of
>> carve out.  The physical address is not valid in a guest.
> I think amdgpu_device_flush_hdp & amdgpu_device_invalidate_hdp need to be modified accordingly.
>
>
> Also, I wonder if BAR resizing could work with APUs?

At least trivial to implement.

The host had to resize the BAR for the client or otherwise the client 
could easily bring down the system.

Christian.

  reply	other threads:[~2022-03-11 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 18:06 [PATCH] drm/amdgpu/gmc: use PCI BARs for APUs in passthrough Alex Deucher
2022-03-11 10:24 ` Michel Dänzer
2022-03-11 10:32   ` Christian König [this message]
2022-03-11 17:43     ` Michel Dänzer
2022-03-16 15:52       ` Michel Dänzer
2022-03-16 15:55         ` Alex Deucher
2022-03-16 15:58           ` Michel Dänzer
2022-03-11 12:17 ` Christian König
2022-03-15 18:13 Alex Deucher
2022-03-16  7:18 ` Christian König
2022-03-16 15:59   ` Michel Dänzer

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=541dc1eb-cf50-17d2-0ae3-5c3cb3dc3ac0@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=michel.daenzer@mailbox.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.