On 12/5/2015 1:07 AM, Alexander Duyck wrote:
We still need to support Windows guest for migration and this is why our
patches keep all changes in the driver since it's impossible to change
Windows kernel.
That is a poor argument. I highly doubt Microsoft is interested in
having to modify all of the drivers that will support direct assignment
in order to support migration. They would likely request something
similar to what I have in that they will want a way to do DMA tracking
with minimal modification required to the drivers.
This totally depends on the NIC or other devices' vendors and they
should make decision to support migration or not. If yes, they would
modify driver.
If just target to call suspend/resume during migration, the feature will
be meaningless. Most cases don't want to affect user during migration
a lot and so the service down time is vital. Our target is to apply
SRIOV NIC passthough to cloud service and NFV(network functions
virtualization) projects which are sensitive to network performance
and stability. From my opinion, We should give a change for device
driver to implement itself migration job. Call suspend and resume
callback in the driver if it doesn't care the performance during migration.
Following is my idea to do DMA tracking.
Inject event to VF driver after memory iterate stage
and before stop VCPU and then VF driver marks dirty all
using DMA memory. The new allocated pages also need to
be marked dirty before stopping VCPU. All dirty memory
in this time slot will be migrated until stop-and-copy
stage. We also need to make sure to disable VF via clearing the
bus master enable bit for VF before migrating these memory.
The ordering of your explanation here doesn't quite work. What needs to
happen is that you have to disable DMA and then mark the pages as dirty.
What the disabling of the BME does is signal to the hypervisor that
the device is now stopped. The ixgbevf_suspend call already supported
by the driver is almost exactly what is needed to take care of something
like this.
This is why I hope to reserve a piece of space in the dma page to do
dummy write. This can help to mark page dirty while not require to stop
DMA and not race with DMA data.
If can't do that, we have to stop DMA in a short time to mark all dma
pages dirty and then reenable it. I am not sure how much we can get by
this way to track all DMA memory with device running during migration. I
need to do some tests and compare results with stop DMA diretly at last
stage during migration.
The question is how we would go about triggering it. I really don't
think the PCI configuration space approach is the right idea.
I wonder
if we couldn't get away with some sort of ACPI event instead. We
already require ACPI support in order to shut down the system
gracefully, I wonder if we couldn't get away with something similar in
order to suspend/resume the direct assigned devices gracefully.
I don't think there is such events in the current spec.
Otherwise, There are two kinds of suspend/resume callbacks.
1) System suspend/resume called during S2RAM and S2DISK.
2) Runtime suspend/resume called by pm core when device is idle.
If you want to do what you mentioned, you have to change PM core and
ACPI spec.
The dma page allocated by VF driver also needs to reserve space
to do dummy write.
No, this will not work. If for example you have a VF driver allocating
memory for a 9K receive how will that work? It isn't as if you can poke
a hole in the contiguous memory.
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
