Message ID | 1450055554-1828-1-git-send-email-helin.zhang@intel.com (mailing list archive) |
---|---|
State | Accepted, archived |
Headers | show |
2015-12-14 09:12, Helin Zhang: > Add a known issue to warn that PF reset event/request is not > handled by any VF drivers till 2.2, and which should be fixed > in the future. > > Signed-off-by: Helin Zhang <helin.zhang@intel.com> Reported-by: David Marchand <david.marchand@6wind.com> [...] > +* Some (possibly all) VF drivers (e.g. i40evf) do not handle any PF reset > + events/requests in VF driver, that means VF driver may not work after a > + PF reset in host side. The workaround is to avoid triggering any PF reset > + events/requests on host side, or wait future fixes. It is not a workaround to wait for a fix ;) Applied without last words, thanks
diff --git a/doc/guides/rel_notes/release_2_2.rst b/doc/guides/rel_notes/release_2_2.rst index a0035b7..a99b6c4 100644 --- a/doc/guides/rel_notes/release_2_2.rst +++ b/doc/guides/rel_notes/release_2_2.rst @@ -273,6 +273,11 @@ Known Issues As the l3fwd example application requires this info, the i40e vector driver must be disabled to benefit of the packet type with i40e. +* Some (possibly all) VF drivers (e.g. i40evf) do not handle any PF reset + events/requests in VF driver, that means VF driver may not work after a + PF reset in host side. The workaround is to avoid triggering any PF reset + events/requests on host side, or wait future fixes. + API Changes -----------
Add a known issue to warn that PF reset event/request is not handled by any VF drivers till 2.2, and which should be fixed in the future. Signed-off-by: Helin Zhang <helin.zhang@intel.com> --- doc/guides/rel_notes/release_2_2.rst | 5 +++++ 1 file changed, 5 insertions(+)