From: Gerd Hoffmann <kraxel@redhat.com>
To: "Zhang, Xiong Y" <xiong.y.zhang@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH V5] drm/i915: Disable stolen memory when i915 runs on qemu
Date: Tue, 18 Apr 2017 13:26:17 +0200 [thread overview]
Message-ID: <1492514777.27392.34.camel@redhat.com> (raw)
In-Reply-To: <8082FF9BCB2B054996454E47167FF4EC1C4BF299@SHSMSX104.ccr.corp.intel.com>
Hi,
> [Zhang, Xiong Y] Thanks for your teach and propose.
> For smbios, could you teach me which type and field could be used ?
qemu adds a specific subsystem id to all virtual devices, so you can use
that to figure you are running on qemu. One good candidate to check is
the host bridge (easy to find due to fixed pci address), another one is
the isa bridge aka lpc (igd already searches for that one for other
reasons). In fact there already is a check for qemu in
intel_detect_pch() ...
cheers,
Gerd
prev parent reply other threads:[~2017-04-18 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 2:08 [PATCH V4] drm/i915: Enhanced disable access to stolen memory as a guest Xiong Zhang
2017-04-05 6:50 ` Daniel Vetter
2017-04-05 7:44 ` [Intel-gfx] " Jani Nikula
2017-04-12 12:20 ` [PATCH V5] drm/i915: Disable stolen memory when i915 runs on qemu Xiong Zhang
2017-04-12 13:21 ` Joonas Lahtinen
2017-04-13 4:15 ` Zhang, Xiong Y
2017-04-13 7:23 ` Tian, Kevin
2017-04-12 18:01 ` [Intel-gfx] " Alex Williamson
2017-04-13 5:44 ` Zhang, Xiong Y
2017-04-13 14:53 ` Alex Williamson
2017-04-14 6:39 ` Zhang, Xiong Y
2017-04-18 11:26 ` Gerd Hoffmann [this message]
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=1492514777.27392.34.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=xiong.y.zhang@intel.com \
--cc=zhenyuw@linux.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;
as well as URLs for NNTP newsgroup(s).