ping
On 2016/8/15 10:53, Zhou Jie wrote:
ping
On 2016/8/2 11:57, Zhou Jie wrote:
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regions.
Signed-off-by: Zhou Jie
---
v2
ping
On 2016/8/2 11:57, Zhou Jie wrote:
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regions.
Signed-off-by: Zhou Jie
---
v2-v3:
1. Call init_completion() in
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regions.
Signed-off-by: Zhou Jie
---
v2-v3:
1. Call init_completion() in vfio_pci_probe.
2. Call reinit_completion() in
Hi, Alex
Clearly this has only been tested for a single instance of an AER error
event and resume per device. Are the things you're intending to block
actually blocked for subsequent events? Note how complete_all() fills
the done field to let all current and future waiters go through and
nowhe
Hi, Alex
On 2016/7/30 1:12, Alex Williamson wrote:
On Tue, 19 Jul 2016 15:32:43 +0800
Zhou Jie wrote:
From: Chen Fan
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar
Hi, Alex
On 2016/7/30 1:11, Alex Williamson wrote:
On Tue, 19 Jul 2016 15:52:45 +0800
Zhou Jie wrote:
From: Chen Fan
An empty commit log is unacceptable for all but the most trivial
patches.
There's also no sign-off on this patch.
Sorry. I should note it.
I also don't know w
ping
On 2016/7/19 16:13, Zhou Jie wrote:
From: Chen Fan
v1-v2:
1. Add aer process to vfio driver.
Chen Fan (2):
vfio : add aer process
vfio : resume notifier
drivers/vfio/pci/vfio_pci.c | 58 -
drivers/vfio/pci/vfio_pci_intrs.c | 18
From: Chen Fan
v1-v2:
1. Add aer process to vfio driver.
Chen Fan (2):
vfio : add aer process
vfio : resume notifier
drivers/vfio/pci/vfio_pci.c | 58 -
drivers/vfio/pci/vfio_pci_intrs.c | 18
drivers/vfio/pci/vfio_pci_private.h
From: Chen Fan
---
drivers/vfio/pci/vfio_pci.c | 28 +++-
drivers/vfio/pci/vfio_pci_intrs.c | 18 ++
drivers/vfio/pci/vfio_pci_private.h | 1 +
include/uapi/linux/vfio.h | 1 +
4 files changed, 47 insertions(+), 1 deletion(-)
diff --
From: Chen Fan
v1-v2:
1. Add aer process to vfio driver.
Chen Fan (1):
vfio : add aer process
root (1):
vfio : resume notifier
drivers/vfio/pci/vfio_pci.c | 58 -
drivers/vfio/pci/vfio_pci_intrs.c | 18
drivers/vfio/pci/vfio_pc
From: Chen Fan
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regions.
Signed-off-by: Zhou Jie
---
drivers/vfio/pci/vfio_pci.c | 30
From: root
---
drivers/vfio/pci/vfio_pci.c | 28 +++-
drivers/vfio/pci/vfio_pci_intrs.c | 18 ++
drivers/vfio/pci/vfio_pci_private.h | 1 +
include/uapi/linux/vfio.h | 1 +
4 files changed, 47 insertions(+), 1 deletion(-)
diff --git
Hi, Alex
On 2016/6/9 23:39, Alexander Duyck wrote:
On Thu, Jun 9, 2016 at 3:14 AM, Zhou Jie wrote:
TO Alex
TO Michael
In your solution you add a emulate PCI bridge to act as
a bridge between direct assigned devices and the host bridge.
Do you mean put all direct assigned devices to
devices unaffected by the bus reset,
be configured on the same virtual bus.
http://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg02989.html
Sincerely,
Zhou Jie
On 2016/6/7 0:04, Alex Duyck wrote:
On Mon, Jun 6, 2016 at 2:18 AM, Zhou Jie wrote:
Hi Alex,
On 2016/1/6 0:18, Alexander
ion?
Sincerely,
Zhou Jie
So
1.- host tells guest to start tracking memory writes
2.- guest acks
3.- migration starts
4.- most memory is migrated
5.- host tells guest to eject device
6.- guest acks
7.- stop vm and migrate rest of state
Sounds about right. The only way this differs from wh
15 matches
Mail list logo
