linux-toradex.git/drivers/net/xen-netback/netback.c, branch v4.10

xen-netback: separate guest side rx code into separate module

2016-10-07T00:37:35+00:00

The netback source module has become very large and somewhat confusing.
This patch simply moves all code related to the backend to frontend (i.e
guest side rx) data-path into a separate rx source module.

This patch contains no functional change, it is code movement and
minimal changes to avoid patch style-check issues.

Signed-off-by: Paul Durrant 
Signed-off-by: David S. Miller

xen-netback: switch to threaded irq for control ring

2016-09-22T12:26:24+00:00

Instead of open coding it use the threaded irq mechanism in
xen-netback.

Signed-off-by: Juergen Gross 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: use hash value from the frontend

2016-05-16T17:35:56+00:00

My recent patch to include/xen/interface/io/netif.h defines a new extra
info type that can be used to pass hash values between backend and guest
frontend.

This patch adds code to xen-netback to use the value in a hash extra
info fragment passed from the guest frontend in a transmit-side
(i.e. netback receive side) packet to set the skb hash accordingly.

Signed-off-by: Paul Durrant 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: pass hash value to the frontend

2016-05-16T17:35:56+00:00

My recent patch to include/xen/interface/io/netif.h defines a new extra
info type that can be used to pass hash values between backend and guest
frontend.

This patch adds code to xen-netback to pass hash values calculated for
guest receive-side packets (i.e. netback transmit side) to the frontend.

Signed-off-by: Paul Durrant 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: add control protocol implementation

2016-05-16T17:35:56+00:00

My recent patch to include/xen/interface/io/netif.h defines a new shared
ring (in addition to the rx and tx rings) for passing control messages
from a VM frontend driver to a backend driver.

A previous patch added the necessary boilerplate for mapping the control
ring from the frontend, should it be created. This patch adds
implementations for each of the defined protocol messages.

Signed-off-by: Paul Durrant 
Cc: Wei Liu 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: add control ring boilerplate

2016-05-16T17:35:56+00:00

My recent patch to include/xen/interface/io/netif.h defines a new shared
ring (in addition to the rx and tx rings) for passing control messages
from a VM frontend driver to a backend driver.

This patch adds the necessary code to xen-netback to map this new shared
ring, should it be created by a frontend, but does not add implementations
for any of the defined protocol messages. These are added in a subsequent
patch for clarity.

Signed-off-by: Paul Durrant 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: fix extra_info handling in xenvif_tx_err()

2016-05-13T05:58:57+00:00

Patch 562abd39 "xen-netback: support multiple extra info fragments
passed from frontend" contained a mistake which can result in an in-
correct number of responses being generated when handling errors
encountered when processing packets containing extra info fragments.
This patch fixes the problem.

Signed-off-by: Paul Durrant 
Reported-by: Jan Beulich 
Cc: Wei Liu 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: support multiple extra info fragments passed from frontend

2016-03-14T02:08:01+00:00

The code does not currently support a frontend passing multiple extra info
fragments to the backend in a tx request. The xenvif_get_extras() function
handles multiple extra_info fragments but make_tx_response() assumes there
is only ever a single extra info fragment.

This patch modifies xenvif_get_extras() to pass back a count of extra
info fragments, which is then passed to make_tx_response() (after
possibly being stashed in pending_tx_info for deferred responses).

Signed-off-by: Paul Durrant 
Cc: Wei Liu 
Acked-by: Wei Liu 
Signed-off-by: David S. Miller

xen-netback: use skb to determine number of required guest Rx requests

2016-01-15T20:13:18+00:00

Using the MTU or GSO size to determine the number of required guest Rx
requests for an skb was subtly broken since these value may change at
runtime.

After 1650d5455bd2dc6b5ee134bd6fc1a3236c266b5b (xen-netback: always
fully coalesce guest Rx packets) we always fully pack a packet into
its guest Rx slots.  Calculating the number of required slots from the
packet length is then easy.

Signed-off-by: David Vrabel 
Signed-off-by: David S. Miller

xen-netback: use RING_COPY_REQUEST() throughout

2015-12-18T15:00:28+00:00

Instead of open-coding memcpy()s and directly accessing Tx and Rx
requests, use the new RING_COPY_REQUEST() that ensures the local copy
is correct.

This is more than is strictly necessary for guest Rx requests since
only the id and gref fields are used and it is harmless if the
frontend modifies these.

This is part of XSA155.

CC: stable@vger.kernel.org
Reviewed-by: Wei Liu 
Signed-off-by: David Vrabel 
Signed-off-by: Konrad Rzeszutek Wilk