On Wed, 28 May 2014, Chen, Tiejun wrote:
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: Wednesday, May 28, 2014 1:36 AM
To: Chen, Tiejun
Cc: anthony.per...@citrix.com; stefano.stabell...@eu.citrix.com;
m...@redhat.com;
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: Wednesday, May 28, 2014 8:24 PM
To: Chen, Tiejun
Cc: Stefano Stabellini; anthony.per...@citrix.com; m...@redhat.com;
kelly.zyta...@amd.com; qemu-devel@nongnu.org;
On Mon, 26 May 2014, Tiejun Chen wrote:
The OpRegion shouldn't be mapped 1:1 because the address in the host
can't be used in the guest directly.
This patch traps read and write access to the opregion of the Intel
GPU config space (offset 0xfc).
The original patch is from Jean Guyader
-Original Message-
From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
Sent: Wednesday, May 28, 2014 1:36 AM
To: Chen, Tiejun
Cc: anthony.per...@citrix.com; stefano.stabell...@eu.citrix.com;
m...@redhat.com; kelly.zyta...@amd.com; qemu-devel@nongnu.org;
The OpRegion shouldn't be mapped 1:1 because the address in the host
can't be used in the guest directly.
This patch traps read and write access to the opregion of the Intel
GPU config space (offset 0xfc).
The original patch is from Jean Guyader jean.guya...@eu.citrix.com
Signed-off-by: Yang
The OpRegion shouldn't be mapped 1:1 because the address in the host
can't be used in the guest directly.
This patch traps read and write access to the opregion of the Intel
GPU config space (offset 0xfc).
The original patch is from Jean Guyader jean.guya...@eu.citrix.com
Signed-off-by: Yang
