From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757479AbcHWKho (ORCPT ); Tue, 23 Aug 2016 06:37:44 -0400 Received: from mail-pf0-f195.google.com ([209.85.192.195]:35512 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752089AbcHWKhd (ORCPT ); Tue, 23 Aug 2016 06:37:33 -0400 From: Joel Fernandes To: namhyung@kernel.org Cc: linux-kernel@vger.kernel.org Subject: Re: [RFC/PATCHSET 0/3] virtio: Implement virtio pstore device (v3) Date: Tue, 23 Aug 2016 03:25:01 -0700 Message-Id: <1471947901-3951-1-git-send-email-agnel.joel@gmail.com> X-Mailer: git-send-email 2.5.0 In-Reply-To: <20160820080744.10344-1-namhyung@kernel.org> References: <20160820080744.10344-1-namhyung@kernel.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Namhyung Kim > Hello, > > This is another iteration of the virtio-pstore work. In this patchset > I addressed most of feedbacks from previous version and drooped the > support for PSTORE_TYPE_CONSOLE for simplicity. It'll be added once the basic Hi Namhyung, This looks like a useful pstore backend. Great work. BTW, Have you considered using -mem-path in Qemu for this purpose? I was thinking about using this, and then somehow have kernel reserve a part of physical memory for the pstore. Then after the crash, or whenever you want to read the contents of the pstore on the host, you could just extract that part of the mem-path file. Any thoughts on what you think about it? In your approach though, you wouldn't need a backing mem-path file which is the size of the guest RAM (which could be as big as the mem-path file). I wonder if the mem-path file can be created sparse, and/or Qemu has support to configure a certain part of guest RAM as file-backed memory and the rest of it from Anonymous memory (not backed by mem-path) so that the size of the mem-path file can be kept at a minimum. Thanks, Joel