> On Mon, 20 Feb 2017 19:42:54 +0800
> Xiong Zhang wrote:
>
> > From: XiongZhang
> >
> > If IGD isn't assigned at 00:02.0 in UPT and host bios enable stolen
> > memory, seabios won't reseave stolen memory in E820 for guest. Then
> > both Intel graphic driver and others in guest could use stolen
>
> On Mon, 20 Feb 2017 19:42:54 +0800
> Xiong Zhang wrote:
>
> > From: XiongZhang
> >
> > If IGD isn't assigned at 00:02.0 in UPT and host bios enable stolen
> > memory, seabios won't reseave stolen memory in E820 for guest. Then
> > both Intel graphic driver and others in guest could use stol
On Mon, 20 Feb 2017 19:42:54 +0800
Xiong Zhang wrote:
> From: XiongZhang
>
> If IGD isn't assigned at 00:02.0 in UPT and host bios enable stolen
> memory, seabios won't reseave stolen memory in E820 for guest. Then
> both Intel graphic driver and others in guest could use stolen
> memory, this
From: XiongZhang
If IGD isn't assigned at 00:02.0 in UPT and host bios enable stolen
memory, seabios won't reseave stolen memory in E820 for guest. Then
both Intel graphic driver and others in guest could use stolen
memory, this will generate system hang. So we should disable stolen
memory in thi
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH] vfio/pci-quirks.c: Disable stolen memory for igd
VFIO
Message-id: 20170220111716.10471-1-xiong.y.zh...@intel.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
From: XiongZhang
If IGD isn't assigned at 00:02.0 in UPT and host bios enable stolen
memory, seabios won't reseave stolen memory in E820 for guest. Then
both Intel graphic driver and others in guest could use stolen
memory, this will generate system hang. So we should disable stolen
memory in thi
