Eric Lee / smarc-fsl-linux-kernel

24 Aug, 2020

1 commit

  • df561f668   treewide: Use fallthrough pseudo-keyword ... Browse Code »

    Replace the existing /* fall through */ comments and its variants with
    the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
    fall-through markings when it is the case.

    [1] https://www.kernel.org/doc/html/v5.7/process/deprecated.html?highlight=fallthrough#implicit-switch-case-fall-through

    Signed-off-by: Gustavo A. R. Silva

    Gustavo A. R. Silva
     

19 Dec, 2018

1 commit

29 Nov, 2018

1 commit

  • 9167f0dcc   scsi: xen-scsifront: mark expected switch fall-through ... Browse Code »

    In preparation to enabling -Wimplicit-fallthrough, mark switch cases where
    we are expecting to fall through.

    Notice that, in this particular case, I replaced "Missed the backend's
    Closing state -- fallthrough" with "fall through - Missed the backend's
    Closing state", which contains the "fall through" annotation at the
    beginnig of the code comment, which is what GCC is expecting to find.

    Signed-off-by: Gustavo A. R. Silva
    Reviewed-by: Juergen Gross
    Signed-off-by: Martin K. Petersen

    Gustavo A. R. Silva
     

19 Jun, 2018

1 commit

13 Jun, 2017

1 commit

02 May, 2017

1 commit

09 Dec, 2016

1 commit

24 Nov, 2016

1 commit

07 Nov, 2016

1 commit

09 Sep, 2015

1 commit

  • 0df4f266b   xen: Use correctly the Xen memory terminologies ... Browse Code »

    Based on include/xen/mm.h [1], Linux is mistakenly using MFN when GFN
    is meant, I suspect this is because the first support for Xen was for
    PV. This resulted in some misimplementation of helpers on ARM and
    confused developers about the expected behavior.

    For instance, with pfn_to_mfn, we expect to get an MFN based on the name.
    Although, if we look at the implementation on x86, it's returning a GFN.

    For clarity and avoid new confusion, replace any reference to mfn with
    gfn in any helpers used by PV drivers. The x86 code will still keep some
    reference of pfn_to_mfn which may be used by all kind of guests
    No changes as been made in the hypercall field, even
    though they may be invalid, in order to keep the same as the defintion
    in xen repo.

    Note that page_to_mfn has been renamed to xen_page_to_gfn to avoid a
    name to close to the KVM function gfn_to_page.

    Take also the opportunity to simplify simple construction such
    as pfn_to_mfn(page_to_pfn(page)) into xen_page_to_gfn. More complex clean up
    will come in follow-up patches.

    [1] http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=e758ed14f390342513405dd766e874934573e6cb

    Signed-off-by: Julien Grall
    Reviewed-by: Stefano Stabellini
    Acked-by: Dmitry Torokhov
    Acked-by: Wei Liu
    Signed-off-by: David Vrabel

    Julien Grall
     

15 Apr, 2015

1 commit

  • ccc9d90a9   xenbus_client: Extend interface to support multi-page ring ... Browse Code »

    Originally Xen PV drivers only use single-page ring to pass along
    information. This might limit the throughput between frontend and
    backend.

    The patch extends Xenbus driver to support multi-page ring, which in
    general should improve throughput if ring is the bottleneck. Changes to
    various frontend / backend to adapt to the new interface are also
    included.

    Affected Xen drivers:
    * blkfront/back
    * netfront/back
    * pcifront/back
    * scsifront/back
    * vtpmfront

    The interface is documented, as before, in xenbus_client.c.

    Signed-off-by: Wei Liu
    Signed-off-by: Paul Durrant
    Signed-off-by: Bob Liu
    Cc: Konrad Wilk
    Cc: Boris Ostrovsky
    Signed-off-by: David Vrabel

    Wei Liu
     

16 Mar, 2015

1 commit

  • 85617dc7e   xen: support suspend/resume in pvscsi frontend ... Browse Code »

    Up to now the pvscsi frontend hasn't supported domain suspend and
    resume. When a domain with an assigned pvscsi device was suspended
    and resumed again, it was not able to use the device any more: trying
    to do so resulted in hanging processes.

    Support suspend and resume of pvscsi devices.

    Signed-off-by: Juergen Gross
    Signed-off-by: David Vrabel

    Juergen Gross
     

06 Oct, 2014

1 commit

03 Oct, 2014

1 commit

23 Sep, 2014

2 commits

  • d9b1e6374   xen-scsifront: use GFP_ATOMIC under spin_lock ... Browse Code »

    This function is only called with a spin_lock held and IRQs disabled.
    The allocation is not allowed to sleep and NOIO is not sufficient, it
    has to be ATOMIC.

    Signed-off-by: Dan Carpenter
    Reviewed-by: Juergen Gross
    Signed-off-by: David Vrabel

    Dan Carpenter
     
  • 8beb8d4c9   xen-scsifront: Add Xen PV SCSI frontend driver ... Browse Code »

    Introduces the Xen pvSCSI frontend. With pvSCSI it is possible for a
    Xen domU to issue SCSI commands to a SCSI LUN assigned to that
    domU. The SCSI commands are passed to the pvSCSI backend in a driver
    domain (usually Dom0) which is owner of the physical device. This
    allows e.g. to use SCSI tape drives in a Xen domU.

    The code is taken from the pvSCSI implementation in Xen done by
    Fujitsu based on Linux kernel 2.6.18.

    Changes from the original version are:
    - port to upstream kernel
    - put all code in just one source file
    - move module to appropriate location in kernel tree
    - adapt to Linux style guide
    - some minor code simplifications
    - replace constants with defines
    - remove not used defines
    - add support for larger SG lists by putting them in a granted page

    Signed-off-by: Juergen Gross
    Acked-by: Christoph Hellwig
    Signed-off-by: David Vrabel

    Juergen Gross