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;
From:   =?UTF-8?q?Marc-Andr=C3=A9=20Lureau?= <marcandre.lureau@redhat.com>
To:     linux-kernel@vger.kernel.org
Cc:     bhe@redhat.com, slp@redhat.com, mst@redhat.com, somlo@cmu.edu,
        xiaolong.ye@intel.com, peterx@redhat.com, qemu-devel@nongnu.org,
        =?UTF-8?q?Marc-Andr=C3=A9=20Lureau?= <marcandre.lureau@redhat.com>
Subject: [PATCH v10 0/4] fw_cfg: add DMA operations & etc/vmcoreinfo support
Date:   Tue, 23 Jan 2018 17:40:37 +0100
Message-Id: <20180123164041.30339-1-marcandre.lureau@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

This series adds DMA operations support to the qemu fw_cfg kernel
module and populates "etc/vmcoreinfo" with vmcoreinfo location
details (since qemu 2.11).

v10:
- merged Peter Xu fix "[PATCH] fw_cfg: don't use DMA mapping for fw_cfg device"
  (fixing fw-cfg+viommu configuration)
- switch back to kalloc'd struct vmci, to fix DMA garbage operations
- do not attempt to write vmcoreinfo if the entry exists but DMA isn't supported
- removed a copy-pasta memset() on write operation error

Marc-André Lureau (4):
  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 | 267 ++++++++++++++++++++++++++++++++++++-----
 kernel/crash_core.c            |   1 +
 2 files changed, 236 insertions(+), 32 deletions(-)

-- 
2.16.0.rc1.1.gef27df75a1