From patchwork Wed May 20 18:12:39 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Maxim Levitsky X-Patchwork-Id: 11560979 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 380AF912 for ; Wed, 20 May 2020 18:12:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 209FA207D4 for ; Wed, 20 May 2020 18:12:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="B4bC87k9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726830AbgETSMt (ORCPT ); Wed, 20 May 2020 14:12:49 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:32298 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726510AbgETSMs (ORCPT ); Wed, 20 May 2020 14:12:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589998367; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=zrw5y7kLFs3H7gZeyqDRl7rn5ygDIp8+n8h/0YJPWVI=; b=B4bC87k9pmNYo0t09OHoGcbRWl3/v9ZoidSc5OpufmRCKfnseMla3PPpqlvbxuCbKFdSav mE6gNgI1sYTTY25nux2Wu9N/urK9E1k4dVJTpQbZMQbjZP3pJ3Cgq+962Ohv2xBc8cSGGE aqtk10XizqCBqOt4DgGwpoAqAimcE1o= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-376-CrulUyWvP3-cx0zX3tnSag-1; Wed, 20 May 2020 14:12:45 -0400 X-MC-Unique: CrulUyWvP3-cx0zX3tnSag-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 01DD11800D42; Wed, 20 May 2020 18:12:44 +0000 (UTC) Received: from starship.redhat.com (unknown [10.35.207.28]) by smtp.corp.redhat.com (Postfix) with ESMTP id A2C2010640E1; Wed, 20 May 2020 18:12:41 +0000 (UTC) From: Maxim Levitsky To: kvm@vger.kernel.org Cc: Michael Jamet , Mika Westerberg , Andreas Noever , linux-usb@vger.kernel.org (open list:THUNDERBOLT DRIVER), Yehezkel Bernat , linux-kernel@vger.kernel.org (open list), Jiri Kosina , Maxim Levitsky Subject: [PATCH 0/1] RFC: Make thunderbolt NHI driver work with kexec Date: Wed, 20 May 2020 21:12:39 +0300 Message-Id: <20200520181240.118559-1-mlevitsk@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org While trying to use kexec on my desktop, which has Titan Ridge Thunderbolt add-on card, I noticed that after a kexec, system hangs for about a minute in the 'wating for udev devices to settle' phase of the boot. I found out that if I unload the thunderbolt driver prior to the kexec, then it works just fine. Looking at the code I see that the driver doeesn't implement .shutdown method, so this on-liner patch points it to the same method that is used on device removal. I don't know if this is the right solution, but it does appear to work just fine with this patch. What do you think? Best regards, Maxim Levitsky Maxim Levitsky (1): thunderbolt: add trivial .shutdown drivers/thunderbolt/nhi.c | 1 + 1 file changed, 1 insertion(+)