From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Tejas Joglekar <Tejas.Joglekar@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
USB <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: John Youn <John.Youn@synopsys.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC PATCH v2 4/4] usb: xhci: Use temporary buffer to consolidate SG
Date: Mon, 18 May 2020 19:21:58 +0300 [thread overview]
Message-ID: <a1845154-2d8d-e63c-a3e7-7a3ed244bd57@linux.intel.com> (raw)
In-Reply-To: <969b5c9f31807635785ecc74b2ae2559ddc3bbeb.1587461220.git.joglekar@synopsys.com>
On 21.4.2020 12.49, Tejas Joglekar wrote:
> The Synopsys xHC has an internal TRB cache of size TRB_CACHE_SIZE for
> each endpoint. The default value for TRB_CACHE_SIZE is 16 for SS and 8
> for HS. The controller loads and updates the TRB cache from the transfer
> ring in system memory whenever the driver issues a start transfer or
> update transfer command.
>
> For chained TRBs, the Synopsys xHC requires that the total amount of
> bytes for all TRBs loaded in the TRB cache be greater than or equal to 1
> MPS. Or the chain ends within the TRB cache (with a last TRB).
>
> If this requirement is not met, the controller will not be able to send
> or receive a packet and it will hang causing a driver timeout and error.
>
> This can be a problem if a class driver queues SG requests with many
> small-buffer entries. The XHCI driver will create a chained TRB for each
> entry which may trigger this issue.
>
> This patch adds logic to the XHCI driver to detect and prevent this from
> happening.
>
> For every (TRB_CACHE_SIZE - 2), we check the total buffer size of
> the SG list and if the last window of (TRB_CACHE_SIZE - 2) SG list length
> and we don't make up at least 1 MPS, we create a temporary buffer to
> consolidate full SG list into the buffer.
>
> We check at (TRB_CACHE_SIZE - 2) window because it is possible that there
> would be a link and/or event data TRB that take up to 2 of the cache
> entries.
>
> We discovered this issue with devices on other platforms but have not
> yet come across any device that triggers this on Linux. But it could be
> a real problem now or in the future. All it takes is N number of small
> chained TRBs. And other instances of the Synopsys IP may have smaller
> values for the TRB_CACHE_SIZE which would exacerbate the problem.
>
> Signed-off-by: Tejas Joglekar <joglekar@synopsys.com>
> ---
> Changes in v2:
> - Removed redundant debug messages
> - Modified logic to remove unnecessary changes in hcd.c
> - Rename the quirk
>
> drivers/usb/host/xhci-ring.c | 2 +-
> drivers/usb/host/xhci.c | 125 +++++++++++++++++++++++++++++++++++++++++++
> drivers/usb/host/xhci.h | 4 ++
> 3 files changed, 130 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
> index a78787bb5133..2fad9474912a 100644
> --- a/drivers/usb/host/xhci-ring.c
> +++ b/drivers/usb/host/xhci-ring.c
> @@ -3291,7 +3291,7 @@ int xhci_queue_bulk_tx(struct xhci_hcd *xhci, gfp_t mem_flags,
>
> full_len = urb->transfer_buffer_length;
> /* If we have scatter/gather list, we use it. */
> - if (urb->num_sgs) {
> + if (urb->num_sgs && !(urb->transfer_flags & URB_DMA_MAP_SINGLE)) {
> num_sgs = urb->num_mapped_sgs;
> sg = urb->sg;
> addr = (u64) sg_dma_address(sg);
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index fe38275363e0..15f06bc6b1ad 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -1256,6 +1256,106 @@ EXPORT_SYMBOL_GPL(xhci_resume);
>
> /*-------------------------------------------------------------------------*/
>
> +static int xhci_map_temp_buffer(struct usb_hcd *hcd, struct urb *urb)
> +{
> + void *temp;
> + int ret = 0;
> + unsigned int len;
> + unsigned int buf_len;
> + enum dma_data_direction dir;
> + struct xhci_hcd *xhci;
> +
> + xhci = hcd_to_xhci(hcd);
> + dir = usb_urb_dir_in(urb) ? DMA_FROM_DEVICE : DMA_TO_DEVICE;
> + buf_len = urb->transfer_buffer_length;
> +
> + temp = kzalloc_node(buf_len, GFP_ATOMIC,
> + dev_to_node(hcd->self.sysdev));
> +
> + if (usb_urb_dir_out(urb))
> + len = sg_pcopy_to_buffer(urb->sg, urb->num_sgs,
> + temp, buf_len, 0);
> +
> + urb->transfer_buffer = temp;
> + urb->transfer_dma = dma_map_single(hcd->self.sysdev,
> + urb->transfer_buffer,
> + urb->transfer_buffer_length,
> + dir);
> +
> + if (dma_mapping_error(hcd->self.sysdev,
> + urb->transfer_dma)) {
> + ret = -EAGAIN;
> + kfree(temp);
> + } else {
> + urb->transfer_flags |= URB_DMA_MAP_SINGLE;
Not sure if using URB_DMA_MAP_SINGLE to flag that this urb is boucebuffered is
appropriate.
If Greg or Alan don't object then it's fine for me as well.
> + }
> +
> + return ret;
> +}
> +
> +static bool xhci_urb_temp_buffer_required(struct usb_hcd *hcd,
> + struct urb *urb)
> +{
> + bool ret = false;
> + unsigned int i;
> + unsigned int len = 0;
> + unsigned int buf_len;
> + unsigned int trb_size;
> + unsigned int max_pkt;
> + struct scatterlist *sg;
> + struct scatterlist *tail_sg;
> +
> + sg = urb->sg;
> + tail_sg = urb->sg;
> + buf_len = urb->transfer_buffer_length;
> + max_pkt = usb_endpoint_maxp(&urb->ep->desc);
> +
> + if (!urb->num_sgs)
> + return ret;
> +
> + if (urb->dev->speed >= USB_SPEED_SUPER)
> + trb_size = TRB_CACHE_SIZE_SS;
> + else
> + trb_size = TRB_CACHE_SIZE_HS;
> +
> + if (urb->transfer_buffer_length != 0 &&
> + !(urb->transfer_flags & URB_NO_TRANSFER_DMA_MAP)) {
> + for_each_sg(urb->sg, sg, urb->num_sgs, i) {
> + len = len + sg->length;
> + if (i > trb_size - 2) {
> + len = len - tail_sg->length;
> + if (len < max_pkt) {
> + ret = true;
> + break;
> + }
> +
> + tail_sg = sg_next(tail_sg);
> + }
> + }
> + }
> + return ret;
> +}
> +
> +static void xhci_unmap_temp_buf(struct urb *urb)
> +{
> + struct scatterlist *sg;
> + unsigned int len;
> + unsigned int buf_len;
> +
> + sg = urb->sg;
> + buf_len = urb->transfer_buffer_length;
> +
> + if (usb_urb_dir_in(urb)) {
> + len = sg_pcopy_from_buffer(urb->sg, urb->num_sgs,
> + urb->transfer_buffer,
> + buf_len,
> + 0);
> + }
> +
> + kfree(urb->transfer_buffer);
> + urb->transfer_buffer = NULL;
clear URB_DMA_MAP_SINGLE from urb->transfer_flags?
Everything else looks good do me.
-Mathias
next prev parent reply other threads:[~2020-05-18 16:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:47 [RFC PATCH v2 0/4] Add logic to consolidate TRBs for Synopsys xHC Tejas Joglekar
2020-04-21 9:48 ` [RFC PATCH v2 1/4] dt-bindings: usb: Add documentation for SG trb cache size quirk Tejas Joglekar
2020-05-06 20:15 ` Rob Herring
2020-05-07 16:03 ` Tejas Joglekar
2020-05-06 20:16 ` Rob Herring
2020-05-07 16:07 ` Tejas Joglekar
2020-04-21 9:48 ` [RFC PATCH v2 2/4] usb: xhci: Set quirk for XHCI_SG_TRB_CACHE_SIZE_QUIRK Tejas Joglekar
2020-04-21 9:48 ` [RFC PATCH v2 3/4] usb: dwc3: Add device property sgl-trb-cache-size-quirk Tejas Joglekar
2020-04-21 9:49 ` [RFC PATCH v2 4/4] usb: xhci: Use temporary buffer to consolidate SG Tejas Joglekar
2020-05-18 8:38 ` Tejas Joglekar
2020-05-18 16:21 ` Mathias Nyman [this message]
2020-05-20 6:41 ` Tejas Joglekar
2020-05-20 16:50 ` Alan Stern
2020-05-20 17:00 ` Tejas Joglekar
2020-05-20 17:44 ` Alan Stern
2020-05-22 1:58 ` Tejas Joglekar
2020-05-22 14:21 ` Alan Stern
2020-05-22 17:22 ` Tejas Joglekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1845154-2d8d-e63c-a3e7-7a3ed244bd57@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=John.Youn@synopsys.com \
--cc=Tejas.Joglekar@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).