From: Matthew Brost <matthew.brost@intel.com>
To: <Simon.Richter@hogyros.de>
Cc: <jeffbai@aosc.io>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2 0/5] drm/xe: enable driver usage on non-4KiB kernels
Date: Tue, 8 Jul 2025 21:35:21 -0700 [thread overview]
Message-ID: <aG3xidZTkbopob1d@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <ffe4cf3f-7f4c-4d24-85cb-b1d80266797f@hogyros.de>
On Wed, Jul 09, 2025 at 01:02:48PM +0900, Simon.Richter@hogyros.de wrote:
> Hi,
>
> this needs to be rebased after the abolition of bo->size — that is either trivial or needs an adjustment in how the size in the parent BO is set.
>
Did this series set bo->size to a different value than the size argument
to drm_gem_private_object_init? If it did, that could be an issue. If
not, s/bo->size/xe_bo_size(bo)
Matt
> Simon
next prev parent reply other threads:[~2025-07-09 4:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 1:11 [PATCH v2 0/5] drm/xe: enable driver usage on non-4KiB kernels Mingcong Bai via B4 Relay
2025-06-13 1:11 ` [PATCH v2 1/5] drm/xe/bo: fix alignment with non-4KiB kernel page sizes Mingcong Bai via B4 Relay
2025-06-13 1:11 ` [PATCH v2 2/5] drm/xe/guc: use GUC_SIZE (SZ_4K) for alignment Mingcong Bai via B4 Relay
2025-06-13 1:11 ` [PATCH v2 3/5] drm/xe/regs: fix RING_CTL_SIZE(size) calculation Mingcong Bai via B4 Relay
2025-06-13 1:11 ` [PATCH v2 4/5] drm/xe: use 4KiB alignment for cursor jumps Mingcong Bai via B4 Relay
2025-06-13 1:11 ` [PATCH v2 5/5] drm/xe/query: use PAGE_SIZE as the minimum page alignment Mingcong Bai via B4 Relay
2025-06-13 14:08 ` ✓ CI.KUnit: success for drm/xe: enable driver usage on non-4KiB kernels Patchwork
2025-06-13 15:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-15 2:35 ` ✓ Xe.CI.Full: " Patchwork
2025-06-16 5:53 ` [PATCH v2 0/5] " Simon Richter
2025-07-09 4:02 ` Simon.Richter
2025-07-09 4:35 ` Matthew Brost [this message]
2025-07-09 5:33 ` Simon Richter
-- strict thread matches above, loose matches on Subject: below --
2025-06-04 2:57 Mingcong Bai via B4 Relay
2025-06-13 0:13 ` Lucas De Marchi
2025-06-13 1:12 ` Mingcong Bai
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=aG3xidZTkbopob1d@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=Simon.Richter@hogyros.de \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeffbai@aosc.io \
/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