From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941168AbcKOGYm (ORCPT ); Tue, 15 Nov 2016 01:24:42 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:35240 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932337AbcKOGYj (ORCPT ); Tue, 15 Nov 2016 01:24:39 -0500 Date: Tue, 15 Nov 2016 15:23:36 +0900 From: Namhyung Kim To: "Michael S. Tsirkin" Cc: virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, LKML , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Anthony Liguori , Anton Vorontsov , Colin Cross , Kees Cook , Tony Luck , Steven Rostedt , Ingo Molnar , Minchan Kim , "Daniel P . Berrange" Subject: Re: [PATCH 2/3] qemu: Implement virtio-pstore device Message-ID: <20161115062336.GA16821@danjae.aot.lge.com> References: <20160820080744.10344-1-namhyung@kernel.org> <20160820080744.10344-3-namhyung@kernel.org> <20160913155710.3q6yj6yqdyozemul@redhat.com> <20160916100547.GC2474@danjae.aot.lge.com> <20161111004710-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20161111004710-mutt-send-email-mst@kernel.org> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 11, 2016 at 12:50:03AM +0200, Michael S. Tsirkin wrote: > On Fri, Sep 16, 2016 at 07:05:47PM +0900, Namhyung Kim wrote: > > On Tue, Sep 13, 2016 at 06:57:10PM +0300, Michael S. Tsirkin wrote: > > > On Sat, Aug 20, 2016 at 05:07:43PM +0900, Namhyung Kim wrote: > > > > + > > > > +/* the index should match to the type value */ > > > > +static const char *virtio_pstore_file_prefix[] = { > > > > + "unknown-", /* VIRTIO_PSTORE_TYPE_UNKNOWN */ > > > > > > Is there value in treating everything unexpected as "unknown" > > > and rotating them as if they were logs? > > > It might be better to treat everything that's not known > > > as guest error. > > > > I was thinking about the version mismatch between the kernel and qemu. > > I'd like to make the device can deal with a new kernel version which > > might implement a new pstore message type. It will be saved as > > unknown but the kernel can read it properly later. > > Well it'll have a different prefix. E.g. if kernel has > two different types they will end up in the same > file, hardly what was wanted. Right, I think it needs to add 'type' info to the filename for unknown type. Thanks, Namhyung