lkml.org 
[lkml]   [2021]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: [PATCH 11/16] iommu/dma: Support PCI P2PDMA pages in dma-iommu map_sg
    Sorry, I think I missed responding to this one so here are the answers:

    On 2021-05-02 7:14 p.m., John Hubbard wrote:
    > On 4/8/21 10:01 AM, Logan Gunthorpe wrote:
    >> When a PCI P2PDMA page is seen, set the IOVA length of the segment
    >> to zero so that it is not mapped into the IOVA. Then, in finalise_sg(),
    >> apply the appropriate bus address to the segment. The IOVA is not
    >> created if the scatterlist only consists of P2PDMA pages.
    >>
    >> Similar to dma-direct, the sg_mark_pci_p2pdma() flag is used to
    >> indicate bus address segments. On unmap, P2PDMA segments are skipped
    >> over when determining the start and end IOVA addresses.
    >>
    >> With this change, the flags variable in the dma_map_ops is
    >> set to DMA_F_PCI_P2PDMA_SUPPORTED to indicate support for
    >> P2PDMA pages.
    >>
    >> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
    >> ---
    >>   drivers/iommu/dma-iommu.c | 66 ++++++++++++++++++++++++++++++++++-----
    >>   1 file changed, 58 insertions(+), 8 deletions(-)
    >>
    >> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
    >> index af765c813cc8..ef49635f9819 100644
    >> --- a/drivers/iommu/dma-iommu.c
    >> +++ b/drivers/iommu/dma-iommu.c
    >> @@ -20,6 +20,7 @@
    >>   #include <linux/mm.h>
    >>   #include <linux/mutex.h>
    >>   #include <linux/pci.h>
    >> +#include <linux/pci-p2pdma.h>
    >>   #include <linux/swiotlb.h>
    >>   #include <linux/scatterlist.h>
    >>   #include <linux/vmalloc.h>
    >> @@ -864,6 +865,16 @@ static int __finalise_sg(struct device *dev,
    >> struct scatterlist *sg, int nents,
    >>           sg_dma_address(s) = DMA_MAPPING_ERROR;
    >>           sg_dma_len(s) = 0;
    >>   +        if (is_pci_p2pdma_page(sg_page(s)) && !s_iova_len) {
    >
    > Newbie question: I'm in the dark as to why the !s_iova_len check is there,
    > can you please enlighten me?

    The loop in iommu_dma_map_sg() will decide what to do with P2PDMA pages.
    If it is to map it with the bus address it will set s_iova_len to zero
    so that no space is allocated in the IOVA. If it is to map it through
    the host bridge, then it it will leave s_iova_len alone and create the
    appropriate mapping with the CPU physical address.

    This condition notices that s_iova_len was set to zero and fills in a SG
    segment with the PCI bus address for that region.


    >
    >> +            if (i > 0)
    >> +                cur = sg_next(cur);
    >> +
    >> +            pci_p2pdma_map_bus_segment(s, cur);
    >> +            count++;
    >> +            cur_len = 0;
    >> +            continue;
    >> +        }
    >> +
    >
    > This is really an if/else condition. And arguably, it would be better
    > to split out two subroutines, and call one or the other depending on
    > the result of if is_pci_p2pdma_page(), instead of this "continue" approach.

    I really disagree here. Putting the exceptional condition in it's own if
    statement and leaving the normal case un-indented is easier to read and
    understand. It also saves an extra level of indentation in code that is
    already starting to look a little squished.


    >>           /*
    >>            * Now fill in the real DMA data. If...
    >>            * - there is a valid output segment to append to
    >> @@ -961,10 +972,12 @@ static int iommu_dma_map_sg(struct device *dev,
    >> struct scatterlist *sg,
    >>       struct iova_domain *iovad = &cookie->iovad;
    >>       struct scatterlist *s, *prev = NULL;
    >>       int prot = dma_info_to_prot(dir, dev_is_dma_coherent(dev), attrs);
    >> +    struct dev_pagemap *pgmap = NULL;
    >> +    enum pci_p2pdma_map_type map_type;
    >>       dma_addr_t iova;
    >>       size_t iova_len = 0;
    >>       unsigned long mask = dma_get_seg_boundary(dev);
    >> -    int i;
    >> +    int i, ret = 0;
    >>         if (static_branch_unlikely(&iommu_deferred_attach_enabled) &&
    >>           iommu_deferred_attach(dev, domain))
    >> @@ -993,6 +1006,31 @@ static int iommu_dma_map_sg(struct device *dev,
    >> struct scatterlist *sg,
    >>           s_length = iova_align(iovad, s_length + s_iova_off);
    >>           s->length = s_length;
    >>   +        if (is_pci_p2pdma_page(sg_page(s))) {
    >> +            if (sg_page(s)->pgmap != pgmap) {
    >> +                pgmap = sg_page(s)->pgmap;
    >> +                map_type = pci_p2pdma_map_type(pgmap, dev,
    >> +                                   attrs);
    >> +            }
    >> +
    >> +            switch (map_type) {
    >> +            case PCI_P2PDMA_MAP_BUS_ADDR:
    >> +                /*
    >> +                 * A zero length will be ignored by
    >> +                 * iommu_map_sg() and then can be detected
    >> +                 * in __finalise_sg() to actually map the
    >> +                 * bus address.
    >> +                 */
    >> +                s->length = 0;
    >> +                continue;
    >> +            case PCI_P2PDMA_MAP_THRU_HOST_BRIDGE:
    >> +                break;
    >> +            default:
    >> +                ret = -EREMOTEIO;
    >> +                goto out_restore_sg;
    >> +            }
    >> +        }
    >> +
    >>           /*
    >>            * Due to the alignment of our single IOVA allocation, we can
    >>            * depend on these assumptions about the segment boundary mask:
    >> @@ -1015,6 +1053,9 @@ static int iommu_dma_map_sg(struct device *dev,
    >> struct scatterlist *sg,
    >>           prev = s;
    >>       }
    >>   +    if (!iova_len)
    >> +        return __finalise_sg(dev, sg, nents, 0);
    >> +
    >
    > ohhh, we're really slicing up this function pretty severely, what with the
    > continue and the early out and several other control flow changes. I think
    > it would be better to spend some time factoring this function into two
    > cases, now that you're adding a second case for PCI P2PDMA. Roughly,
    > two subroutines would do it.

    I don't see how we can factor this into two cases. The SGL may contain
    normal pages or P2PDMA pages or a mix of both and we have to create an
    IOVA area for all the regions that map the CPU physical address (ie
    normal pages and some P2PDMA pages) then also insert segments for any
    PCI bus address.

    > As it is, this leaves behind a routine that is extremely hard to mentally
    > verify as correct.

    Yes, this is tricky code, but not that incomprehensible. Most of the
    difficulty is in understanding how it works before adding the P2PDMA bits.

    There are two loops: one to prepare the IOVA region and another to fill
    in the SGL. We have to add cases in both loops to skip the segments that
    need to be mapped with the bus address in the first loop, and insert the
    dma SGL segments in the second loop.

    Logan

    \
     
     \ /
      Last update: 2021-05-07 02:00    [W:3.063 / U:0.044 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site