Received: by 10.223.164.202 with SMTP id h10csp771530wrb; Thu, 23 Nov 2017 06:03:19 -0800 (PST) X-Google-Smtp-Source: AGs4zMZwSr6cpebMYyVbSm325q9o7Jgjcfz1WEG3+ZuQj+u03AVOzZmz3oDVfXxW06E0uLxU1TQS X-Received: by 10.84.252.10 with SMTP id x10mr18948465pll.216.1511445799305; Thu, 23 Nov 2017 06:03:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511445799; cv=none; d=google.com; s=arc-20160816; b=vK8/EtagtzE+NMuILHQVnPbN3IuUCJHAwfQNYxf4Zbfqh+WmtDiWfOiSXTnQmI6x2Z PjcN4nUp+qKWaEEHWRz+dxXaRcxtPCGkJDN2O3Rzefe7m9YeyGCPb1rzkygmyJ6D6OAb jsAhnZSA4QqFK4cH6ojmJvtUbUFGjr81VyqLeEuyozrQiCbkm2D7NmVyJY4rfJDPr+co ziMubcbchS5yOLATaV5AyKdjHvTHha6Qehi2gJ6g1UmyIlzEHT2Fh/N6PxXpiqXzXj1t 9pvM8BcFHRwtXRlaH57xm8Tqn/chmTF93G5x6M+YCyB2T5kySS7OUFBb3zQAluTrTHSZ u5NA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:arc-authentication-results; bh=aoFPB0XazycgrdxH8T+MqPruylYpiu0/CFklvfPKZBg=; b=TkN+MYmOc89ZgVggbVxOpRR9gyFuvhW8lWc7jcRQ3zyRm4AXhjYsmP7J4MA42Nu7F2 Eob/LgHE21ck/cMw6ZqBu1mcJSnKGQaxuCODA0Dbp+iZsogA8xh8KaVj9g5z99eXXtW7 Bo9B1WuUkhI/4c9KX8IQfTDuTfnlxZbCvYJuB+m52kjOmjrDAezup/KfY0WHGFdYVgZN ujdxkMCp60TAwN83RFAhfO3anXydOfzcGU3W2Llej5k0xN+cM6wPFp8nHyeSbelL2m8t jNjB02ast+MxOYa9ZM/fJOsejI3ORZ7VhzOanr8vDPIcq69HMkjLE5b+Zazr6ZYaXKV8 GtJA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b15si17775245pfl.199.2017.11.23.06.03.07; Thu, 23 Nov 2017 06:03:19 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753038AbdKWOCO (ORCPT + 75 others); Thu, 23 Nov 2017 09:02:14 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34706 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752968AbdKWOCL (ORCPT ); Thu, 23 Nov 2017 09:02:11 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1E4E4FC7C2; Thu, 23 Nov 2017 14:02:11 +0000 (UTC) Received: from localhost (ovpn-112-71.ams2.redhat.com [10.36.112.71]) by smtp.corp.redhat.com (Postfix) with ESMTP id 48F6960F89; Thu, 23 Nov 2017 14:02:07 +0000 (UTC) From: =?UTF-8?q?Marc-Andr=C3=A9=20Lureau?= To: linux-kernel@vger.kernel.org Cc: somlo@cmu.edu, xiaolong.ye@intel.com, qemu-devel@nongnu.org, mst@redhat.com, =?UTF-8?q?Marc-Andr=C3=A9=20Lureau?= Subject: [PATCH v8 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support Date: Thu, 23 Nov 2017 15:02:01 +0100 Message-Id: <20171123140206.3911-1-marcandre.lureau@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Thu, 23 Nov 2017 14:02:11 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, This series adds DMA operations support to the qemu fw_cfg kernel module and populates "etc/vmcoreinfo" with vmcoreinfo location details. Note: the support for this entry handling has been merged for upcoming qemu release (2.11). v8: - fix ltp again: bring back kmalloc() for DMA memory (see "What memory is DMA'able?" limitations in Documentation/DMA-API-HOWTO.txt) Interestingly, it didn't fail when the module was linked in.. v7: - add a patch to fix driver remove() - remove DMA operatiom timeout (qemu finishes sync today) - synchronize the DMA transfer before reading from CPU - removed kmalloc() use static allocation instead - drop some r-b tags v6: - change acpi_acquire_global_lock() error to return EINVAL (instead of EBUSY) - replace 0 as pointer argument for NULL - add Gabriel r-b/a-b tags v5: - resent to CC kdump people on the paddr_vmcoreinfo_note() export patch v4: - export paddr_vmcoreinfo_note() to fix fw_cfg.ko build - fix build with !CONFIG_CRASH_CORE - replace the unbounded yield() loop with a usleep_range() loop and a 200ms timeout - do not write vmcoreinfo entry when running the kdump kernel (D. Hatayama) - drop the experimental sysfs write support patch from this series v3: (thanks kbuild) - add "fw_cfg: fix the command line module name" patch - fix build of "fw_cfg: add DMA register" with CONFIG_FW_CFG_SYSFS_CMDLINE=y - fix 'Wshift-count-overflow' v2: - use platform device for dma mapping - add etc/vmcoreinfo patch - some code cleanups Marc-André Lureau (5): fw_cfg: fix driver remove fw_cfg: add DMA register fw_cfg: do DMA read operation crash: export paddr_vmcoreinfo_note() fw_cfg: write vmcoreinfo details drivers/firmware/qemu_fw_cfg.c | 283 ++++++++++++++++++++++++++++++++++++----- kernel/crash_core.c | 1 + 2 files changed, 254 insertions(+), 30 deletions(-) -- 2.15.0.277.ga3d2ad2c43 From 1605710912591754523@xxx Wed Jul 11 16:07:36 +0000 2018 X-GM-THRID: 1585342434913349074 X-Gmail-Labels: Inbox,Category Forums,Downloaded_2018-07