From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
"Wang, Zhi A" <zhi.a.wang@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
"Lv, Zhiyuan" <zhiyuan.lv@intel.com>
Subject: Re: Wrt golden MMIO/CFG snaphot in GVT-g
Date: Fri, 27 May 2016 14:38:35 +0300 [thread overview]
Message-ID: <1464349115.6972.15.camel@linux.intel.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F87B924@SHSMSX101.ccr.corp.intel.com>
On pe, 2016-05-27 at 10:09 +0000, Tian, Kevin wrote:
> Curious why leaking BIOS configuration to VM is a security problem…
> Can someone elaborate this view?
>
Hi,
It is a potential vector in case we are blindly reading everything but
blacklisted registers. Whitelisting would make it less so.
But bigger problem is that it is a one more variable to the VM
boot/operation; one could make a server farm non-operational by
changing BIOS settings from one machine whose tasks are migrated to
other servers.
I think both are rather big inconvenience compared to making one-time
golden MMIO snapshot for strange SKUs.
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:[~2016-05-27 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 10:05 FW: Wrt golden MMIO/CFG snaphot in GVT-g Wang, Zhi A
2016-05-27 10:09 ` Tian, Kevin
2016-05-27 11:38 ` Joonas Lahtinen [this message]
2016-06-03 12:19 ` Tian, Kevin
2016-05-27 11:32 ` FW: " Joonas Lahtinen
2016-05-31 14:01 ` Zhiyuan Lv
2016-06-01 12:49 ` Joonas Lahtinen
2016-06-01 14:40 ` Zhiyuan Lv
2016-06-03 12:36 ` Tian, Kevin
2016-06-08 9:23 ` Joonas Lahtinen
2016-06-15 8:05 ` Tian, Kevin
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=1464349115.6972.15.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=zhi.a.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox