All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhi Wang <zhi.a.wang@intel.com>
To: chris@chris-wilson.co.uk, zhiyuan.lv@intel.com,
	kevin.tian@intel.com, tvrtko.ursulin@linux.intel.com,
	intel-gfx@lists.freedesktop.org
Subject: [PATCH v8 02/10] drm/i915: Use offsetof() to calculate the offset of members in PVINFO page
Date: Wed,  8 Jun 2016 11:30:20 -0400	[thread overview]
Message-ID: <1465399828-17082-3-git-send-email-zhi.a.wang@intel.com> (raw)
In-Reply-To: <1465399828-17082-1-git-send-email-zhi.a.wang@intel.com>

To get the offset of the members in PVINFO page, offsetof() looks much
better than the tricky approach in current code.

v7:

- Move "offsetof()" modification into a dedicated patch. (Joonas)

Suggested-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Signed-off-by: Zhi Wang <zhi.a.wang@intel.com>
---
 drivers/gpu/drm/i915/i915_pvinfo.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/i915_pvinfo.h b/drivers/gpu/drm/i915/i915_pvinfo.h
index 68bdf60..7b3cec4 100644
--- a/drivers/gpu/drm/i915/i915_pvinfo.h
+++ b/drivers/gpu/drm/i915/i915_pvinfo.h
@@ -104,7 +104,7 @@ struct vgt_if {
 } __packed;
 
 #define vgtif_reg(x) \
-	_MMIO((VGT_PVINFO_PAGE + (long)&((struct vgt_if *)NULL)->x))
+	_MMIO((VGT_PVINFO_PAGE + offsetof(struct vgt_if, x)))
 
 /* vGPU display status to be used by the host side */
 #define VGT_DRV_DISPLAY_NOT_READY 0
-- 
1.9.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-06-08 15:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 15:30 [PATCH v8 00/10] Introduce the implementation of GVT context Zhi Wang
2016-06-08 15:30 ` [PATCH v8 01/10] drm/i915: Factor out i915_pvinfo.h Zhi Wang
2016-06-08 15:30 ` Zhi Wang [this message]
2016-06-08 15:30 ` [PATCH v8 03/10] drm/i915: Fold vGPU active check into inner functions Zhi Wang
2016-06-08 15:30 ` [PATCH v8 04/10] drm/i915: gvt: Introduce the basic architecture of GVT-g Zhi Wang
2016-06-08 15:30 ` [PATCH v8 05/10] drm/i915: Introduce host graphics memory partition for GVT-g Zhi Wang
2016-06-08 15:30 ` [PATCH v8 06/10] drm/i915: Make ring buffer size of a LRC context configurable Zhi Wang
2016-06-08 16:03   ` Chris Wilson
2016-06-08 15:30 ` [PATCH v8 07/10] drm/i915: Make addressing mode bits in context descriptor configurable Zhi Wang
2016-06-08 16:08   ` Chris Wilson
2016-06-08 16:13     ` Wang, Zhi A
2016-06-08 15:30 ` [PATCH v8 08/10] drm/i915: Introduce execlist context status change notification Zhi Wang
2016-06-08 15:30 ` [PATCH v8 09/10] drm/i915: Support LRC context single submission Zhi Wang
2016-06-08 15:30 ` [PATCH v8 10/10] drm/i915: Introduce GVT context creation API Zhi Wang
2016-06-08 16:00 ` ✗ Ro.CI.BAT: warning for Introduce the implementation of GVT context (rev6) Patchwork
2016-06-08 16:00 ` [PATCH v8 00/10] Introduce the implementation of GVT context Chris Wilson
2016-06-08 16:05   ` Wang, Zhi A

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=1465399828-17082-3-git-send-email-zhi.a.wang@intel.com \
    --to=zhi.a.wang@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kevin.tian@intel.com \
    --cc=tvrtko.ursulin@linux.intel.com \
    --cc=zhiyuan.lv@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 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.