-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adapt to new (v2) VFIO migration interface #654
Comments
Main email thread: https://lore.kernel.org/all/[email protected]/ |
Looks like the mmaped migration region isn't supported with the new interface. |
I've started adopting the new API here: https://github.com/tmakatos/muser/tree/migration-v2 Next, I'll start implementing Python tests. |
@likebreath sorry, we don't right now, but we'd be very happy if somebody wanted to make some proposals :) |
@jlevon Thank you for the quick response. I would love to help and contribute. I know @tmakatos had a WIP branch for this work: https://github.com/tmakatos/muser/tree/migration-v2. Is this the right place to pick-up the work? Also, can you please provide me a summary about what are the missing bits? Thank you. |
Yes, this is the right branch, specifically this commit: tmakatos@059aa82
Unfortunately it's been so long that I forgot the details, I would have to start from the beginning (re-read the kernel API, re-read my patch etc.). Could you try to see whether the commit makes sense and if not I can see how I could help? |
Sure. I will let you know when I need your inputs. I will also keep you posted when I have a timeline for this work. |
Alex Williamson says:
These should be considered deprecated from the kernel interface. I
hope there are plans for vfio-user to adopt the new interface that's
currently available in linux-next and intended for v5.18.
Which is this:
Need to investigate and possibly adopt these changes.
The text was updated successfully, but these errors were encountered: