Could you elaborate on the concrete issue which you're seeing?
I guess the issue occurs when passed through pci device
is unplugged. But in that case, the region was occupied by
the device so that qemu haven't seen io on the area anyway.
And why GPFN_LOW_MMIO independently of addr? Shouldn't it
Isaku Yamahata wrote:
Could you elaborate on the concrete issue which you're seeing?
I guess the issue occurs when passed through pci device
is unplugged. But in that case, the region was occupied by
the device so that qemu haven't seen io on the area anyway.
For assigning a device to a hvm
On Tue, Mar 03, 2009 at 05:32:42PM +0800, Zhang, Xiantao wrote:
Isaku Yamahata wrote:
Could you elaborate on the concrete issue which you're seeing?
I guess the issue occurs when passed through pci device
is unplugged. But in that case, the region was occupied by
the device so that qemu
On Tue, Mar 03, 2009 at 01:47:49PM +0800, Zhang, Xiantao wrote:
Hi, Tristan
Attached patch targets for fixing the issue when assigning the devices
with 64-bit bars. Current logic may deem one 64-bit bar as two 32-bit bars,
and make the system crash finally.
Merged, thanks!
Do you
We only found it when assigning the device with vt-d. Since qemu doesn't have
the device with 64-bit bars, so maybe no issue.
Xiantao
Tristan Gingold wrote:
On Tue, Mar 03, 2009 at 01:47:49PM +0800, Zhang, Xiantao wrote:
Hi, Tristan
Attached patch targets for fixing the issue when
