public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] habanalabs second pull request for kernel 5.8
Date: Mon, 25 May 2020 08:28:19 +0300	[thread overview]
Message-ID: <20200525052819.GA19318@ogabbay-VM> (raw)

Hello Greg,

This is the second pull request for habanalabs driver for kernel 5.8.

It contains important improvements to our MMU code and our ASIC reset code.

Please see the tag message for more details on what this pull request
contains.

Thanks,
Oded

The following changes since commit 709b41b56a16a5901a89dcaeb75d2233f80d9e55:

  misc: rtsx: Remove unnecessary rts5249_set_aspm(), rts5260_set_aspm() (2020-05-22 09:38:14 +0200)

are available in the Git repository at:

  git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-next-2020-05-25

for you to fetch changes up to 8ff5f4fd40df9525675ea0e512da4cec65d646eb:

  habanalabs: handle MMU cache invalidation timeout (2020-05-25 08:17:57 +0300)

----------------------------------------------------------------
This tag contains the following changes for kernel 5.8:

- Improve MMU cache invalidation code and handle case where the
  invalidation doesn't finish in a reasonable time.

- Remove the option to perform soft-reset to GAUDI. Soft-reset is where the
  driver only resets the compute and DMA engines of the ASIC. This is not
  relevant to GAUDI as we must also reset the NIC ports. And when we reset
  the NIC ports, we must also reset other stuff so we prefer to just do
  hard-reset (where we reset the entire ASIC except for PCIe).

- Fail the hard-reset procedure in case we still have user processes which
  have active file-descriptors on a device. Doing hard-reset in that case
  can result in a kernel panic because of gen_pool checks

- Don't initialize the default wait callback of dma_buf with the default
  wait function as that's the default...

----------------------------------------------------------------
Daniel Vetter (1):
      habanalabs: don't set default fence_ops->wait

Oded Gabbay (1):
      habanalabs: GAUDI does not support soft-reset

Omer Shpigelman (4):
      habanalabs: improve MMU cache invalidation code
      habanalabs: add print for soft reset due to event
      habanalabs: don't allow hard reset with open processes
      habanalabs: handle MMU cache invalidation timeout

 drivers/misc/habanalabs/command_submission.c |  1 -
 drivers/misc/habanalabs/device.c             | 23 ++++++---
 drivers/misc/habanalabs/gaudi/gaudi.c        | 74 ++++++++++++++++++----------
 drivers/misc/habanalabs/goya/goya.c          | 35 ++++++++-----
 drivers/misc/habanalabs/habanalabs.h         | 10 ++--
 drivers/misc/habanalabs/memory.c             | 35 ++++++++++---
 drivers/misc/habanalabs/sysfs.c              |  5 ++
 7 files changed, 126 insertions(+), 57 deletions(-)

             reply	other threads:[~2020-05-25  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  5:28 Oded Gabbay [this message]
2020-05-25  6:50 ` [git pull] habanalabs second pull request for kernel 5.8 Greg KH

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=20200525052819.GA19318@ogabbay-VM \
    --to=oded.gabbay@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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