From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: "Li, Weinan Z" <weinan.z.li@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [PATCH v4] drm/i915/gvt: return the correct usable aperture size under gvt environment
Date: Thu, 18 May 2017 11:28:04 +0300 [thread overview]
Message-ID: <1495096084.9811.1.camel@linux.intel.com> (raw)
In-Reply-To: <9BD218709B5F2A4F96F08B4A3B98A89768551312@SHSMSX101.ccr.corp.intel.com>
On pe, 2017-05-12 at 03:20 +0000, Li, Weinan Z wrote:
>
> Thanks Joonas' guidance.
> I add 4 labels in intel_vgt_balloon for cleaning up ballooned space, the reserved size
> will increase when one balloon space reserve success, and will clean up if anyone reserve
> fail step by step.
Yes, there could still be vgt_deballoon_space function to further
reduce code duplication. The labels should begin with err_, like
elsewhere in in the driver.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-18 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 2:59 [PATCH v4] drm/i915/gvt: return the correct usable aperture size under gvt environment Weinan Li
2017-05-10 3:24 ` ✓ Fi.CI.BAT: success for drm/i915/gvt: return the correct usable aperture size under gvt environment (rev2) Patchwork
2017-05-10 10:42 ` [PATCH v4] drm/i915/gvt: return the correct usable aperture size under gvt environment Joonas Lahtinen
2017-05-11 6:51 ` Li, Weinan Z
2017-05-11 12:55 ` Joonas Lahtinen
2017-05-12 3:20 ` Li, Weinan Z
2017-05-18 8:28 ` Joonas Lahtinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-10 2:47 Weinan Li
2017-05-10 3:01 ` Li, Weinan Z
2017-05-12 0:08 ` kbuild test robot
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=1495096084.9811.1.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=weinan.z.li@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