Isaku Yamahata wrote:
On Thu, Mar 05, 2009 at 11:55:10AM +0800, Zhang, Xiantao wrote:
Isaku Yamahata wrote:
On Wed, Mar 04, 2009 at 05:26:41PM +0800, Zhang, Xiantao wrote:
So far, we just found the msi-x case. Maybe we will add msi-x
support later, so this fix is also required.
Okay,
On Fri, Mar 06, 2009 at 10:11:42AM +0800, Zhang, Xiantao wrote:
Isaku Yamahata wrote:
On Thu, Mar 05, 2009 at 11:55:10AM +0800, Zhang, Xiantao wrote:
Isaku Yamahata wrote:
On Wed, Mar 04, 2009 at 05:26:41PM +0800, Zhang, Xiantao wrote:
So far, we just found the msi-x case. Maybe we will
Isaku Yamahata wrote:
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
On Wed, Mar 04, 2009 at 05:26:41PM +0800, Zhang, Xiantao wrote:
So far, we just found the msi-x case. Maybe we will add msi-x support later,
so this fix is also required.
Okay, makes sense.
And why GPFN_LOW_MMIO independently of addr? Shouldn't it be aware
of io_ranges[]?
For the
Isaku Yamahata wrote:
On Wed, Mar 04, 2009 at 05:26:41PM +0800, Zhang, Xiantao wrote:
So far, we just found the msi-x case. Maybe we will add msi-x
support later, so this fix is also required.
Okay, makes sense.
And why GPFN_LOW_MMIO independently of addr? Shouldn't it be aware
of
On Thu, Mar 05, 2009 at 11:55:10AM +0800, Zhang, Xiantao wrote:
Isaku Yamahata wrote:
On Wed, Mar 04, 2009 at 05:26:41PM +0800, Zhang, Xiantao wrote:
So far, we just found the msi-x case. Maybe we will add msi-x
support later, so this fix is also required.
Okay, makes sense.
And
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
PATCH: Fix the logic when deassign the mmio ranges for vti-domain.
When de-assign the mmio range, it should resume its original value
for p2m value, otherwise, it may fail to determin mmio range's type.
Signed-off-by: Xiantao Zhang xiantao.zh...@intel.com
diff -r 67f2e14613ef
10 matches
Mail list logo
