From: "Christian König" <christian.koenig@amd.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Question on how i915/GEM is handling page faults
Date: Wed, 20 Nov 2019 13:18:32 +0100 [thread overview]
Message-ID: <235eafec-1a23-c354-d7a0-65cf1f60402a@amd.com> (raw)
Hi Daniel,
how does i915/GEM lock dma_resv objects for CPU page faulting?
I've been wondering if a good bunch of ttm_bo_vm_reserve() wouldn't be
better placed in the common dma_resv.c file.
Regards,
Christian.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>
Subject: [Intel-gfx] Question on how i915/GEM is handling page faults
Date: Wed, 20 Nov 2019 13:18:32 +0100 [thread overview]
Message-ID: <235eafec-1a23-c354-d7a0-65cf1f60402a@amd.com> (raw)
Message-ID: <20191120121832.54d1LcNqTSSIsmftThwFkFFmgSNnfm1Vf8AD9hbG6_4@z> (raw)
Hi Daniel,
how does i915/GEM lock dma_resv objects for CPU page faulting?
I've been wondering if a good bunch of ttm_bo_vm_reserve() wouldn't be
better placed in the common dma_resv.c file.
Regards,
Christian.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-11-20 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 12:18 Christian König [this message]
2019-11-20 12:18 ` [Intel-gfx] Question on how i915/GEM is handling page faults 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=235eafec-1a23-c354-d7a0-65cf1f60402a@amd.com \
--to=christian.koenig@amd.com \
--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 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.