From: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
To: Matthew Auld <matthew.auld@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 1/5] xe: sync small-bar uapi
Date: Mon, 3 Apr 2023 02:46:36 +0300 [thread overview]
Message-ID: <4350fc32-1285-60e8-e519-738f3769bc78@intel.com> (raw)
In-Reply-To: <20230329115642.244296-2-matthew.auld@intel.com>
btw, The kernel patch hasn't been merged into drm-xe yet, are there any
blockers to merge it?
Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
On 3/29/23 2:56 PM, Matthew Auld wrote:
> We need a couple new fields for the region query and the new flag to
> ensure the buffer is CPU accessible.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> ---
> include/drm-uapi/xe_drm.h | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
> index 593b01ba..441b377b 100644
> --- a/include/drm-uapi/xe_drm.h
> +++ b/include/drm-uapi/xe_drm.h
> @@ -169,7 +169,9 @@ struct drm_xe_query_mem_usage {
> __u32 max_page_size;
> __u64 total_size;
> __u64 used;
> - __u64 reserved[8];
> + __u64 cpu_visible_size;
> + __u64 cpu_visible_used;
> + __u64 reserved[6];
> } regions[];
> };
>
> @@ -270,6 +272,7 @@ struct drm_xe_gem_create {
> */
> #define XE_GEM_CREATE_FLAG_DEFER_BACKING (0x1 << 24)
> #define XE_GEM_CREATE_FLAG_SCANOUT (0x1 << 25)
> +#define XE_GEM_CREATE_FLAG_NEEDS_VISIBLE_VRAM (0x1 << 26)
> __u32 flags;
>
> /**
next prev parent reply other threads:[~2023-04-02 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 11:56 [igt-dev] [PATCH i-g-t 0/5] IGT bits for small-bar Matthew Auld
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 1/5] xe: sync small-bar uapi Matthew Auld
2023-04-02 23:46 ` Gwan-gyeong Mun [this message]
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 2/5] lib/xe: add visible vram helpers Matthew Auld
2023-04-03 9:18 ` Gwan-gyeong Mun
2023-04-03 12:39 ` Matthew Auld
2023-04-03 14:17 ` Gwan-gyeong Mun
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 3/5] tests/xe: handle small-bar systems Matthew Auld
2023-04-05 12:53 ` Gwan-gyeong Mun
2023-05-17 17:03 ` Kamil Konieczny
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 4/5] tests/xe/query: extend for CPU visible accounting Matthew Auld
2023-04-17 5:54 ` Gwan-gyeong Mun
2023-03-29 11:56 ` [igt-dev] [PATCH i-g-t 5/5] tests/xe/mmap: sanity check small-bar Matthew Auld
2023-03-29 12:39 ` [igt-dev] ✓ Fi.CI.BAT: success for IGT bits for small-bar Patchwork
2023-03-30 2:29 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-05-17 14:40 ` [igt-dev] ✗ Fi.CI.BUILD: failure for IGT bits for small-bar (rev2) Patchwork
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=4350fc32-1285-60e8-e519-738f3769bc78@intel.com \
--to=gwan-gyeong.mun@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox