From: Deepak Rawat <drawat.floss@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-hyperv@vger.kernel.org,
Stephen Hemminger <sthemmin@microsoft.com>,
David Airlie <airlied@linux.ie>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>,
dri-devel@lists.freedesktop.org,
Michael Kelley <mikelley@microsoft.com>,
Jork Loeser <jloeser@microsoft.com>, Wei Hu <weh@microsoft.com>,
K Y Srinivasan <kys@microsoft.com>
Subject: Re: [RFC PATCH 1/2] drm/hyperv: Add DRM driver for hyperv synthetic video device
Date: Mon, 22 Jun 2020 15:43:21 -0700 [thread overview]
Message-ID: <af5ebef18bcce1272ab1e02daa0b04cc4284ed9e.camel@gmail.com> (raw)
In-Reply-To: <20200622151913.GA655276@ravnborg.org>
>
> Just a buch of drive-by comments while browsing the code.
> In general code looks good, especialyl for a v1.
>
> There is a few places that triggers warnings with checkpatch --strict
> Most looks like things that should be fixed.
>
>
Thanks Sam for the review. Will take care of the suggestions in next
iteration.
Response inlined below:
> > +struct pipe_msg_hdr {
> > + u32 type;
> > + u32 size; /* size of message after this field */
> > +} __packed;
> > +
> > +struct hvd_screen_info {
> > + u16 width;
> > + u16 height;
> > +} __packed;
> > +
> > +struct synthvid_msg_hdr {
> > + u32 type;
> > + u32 size; /* size of this header + payload after this field*/
> Add space before closing "*/"
>
> I wonder what is the difference between what is considered a message
> and
> what is considered payload in the above comments.
> Maybe that just because I do not know this stuff at all and the
> comment
> can be ignored.
message = struct pipe_msg_hdr + struct synthvid_msg_hdr + payload
Will try to make it more clear.
>
> > +} __packed;
> > +
> > +struct synthvid_version_req {
> > + u32 version;
> > +} __packed;
> > +
> > +struct synthvid_version_resp {
> > + u32 version;
> > + u8 is_accepted;
> > + u8 max_video_outputs;
> > +} __packed;
> > +
> > +struct synthvid_vram_location {
> > + u64 user_ctx;
> > + u8 is_vram_gpa_specified;
> > + u64 vram_gpa;
> > +} __packed;
> Not an alignmnet friendly layout - but I guess the layout is fixed.
> Same goes in otther places.
Yes nothing can be done for this.
>
> > +static int synthvid_update_situation(struct hv_device *hdev, u8
> > active, u32 bpp,
> > + u32 w, u32 h, u32 pitch)
> > +{
> > + struct synthvid_msg msg;
>
> Sometimes synthvid_msg is hv->init_buf.
> Sometimes a local variable.
> I wonder why there is a difference.
When a reply is expected, hv->init_buf should be used, though I haven't
verified this. Just kept the same logic as in framebuffer driver.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-06-22 22:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 11:06 [RFC PATCH 0/2] DRM driver for hyper-v synthetic video device Deepak Rawat
2020-06-22 11:06 ` [RFC PATCH 1/2] drm/hyperv: Add DRM driver for hyperv " Deepak Rawat
2020-06-22 12:46 ` Gerd Hoffmann
2020-06-22 22:20 ` Deepak Rawat
2020-06-23 9:42 ` Daniel Vetter
2020-06-23 16:17 ` Gerd Hoffmann
2020-06-25 0:47 ` Deepak Rawat
2020-06-22 15:19 ` Sam Ravnborg
2020-06-22 22:43 ` Deepak Rawat [this message]
2020-06-23 7:59 ` Thomas Zimmermann
2020-06-23 9:12 ` Deepak Rawat
2020-06-23 9:19 ` Thomas Zimmermann
2020-06-23 2:31 ` Dexuan Cui
2020-06-23 6:48 ` Deepak Rawat
2020-06-23 21:58 ` Dexuan Cui
2020-06-22 11:06 ` [RFC PATCH 2/2] MAINTAINERS: Add maintainer for hyperv " Deepak Rawat
2020-06-28 23:01 ` [RFC PATCH 0/2] DRM driver for hyper-v synthetic " Daniel Vetter
2020-09-10 8:19 [RFC PATCH 1/2] drm/hyperv: Add DRM driver for hyperv " Tang, Shaofeng
2020-09-11 0:38 ` Deepak Rawat
2020-11-15 9:14 ` Thomas Zimmermann
2020-11-15 17:55 ` Deepak Rawat
2020-11-15 18:58 ` Thomas Zimmermann
2020-11-16 9:58 ` Daniel Vetter
2020-11-16 16:36 ` Deepak Rawat
2020-09-28 15:58 Marcin Skarbek
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=af5ebef18bcce1272ab1e02daa0b04cc4284ed9e.camel@gmail.com \
--to=drawat.floss@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=haiyangz@microsoft.com \
--cc=jloeser@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=sam@ravnborg.org \
--cc=sthemmin@microsoft.com \
--cc=weh@microsoft.com \
--cc=wei.liu@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).