From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH v8 05/11] xen: grant_table: implement grant_table_warn_active_grants() Date: Mon, 13 Jul 2015 10:24:46 -0400 Message-ID: <20150713142446.GA7477@l.oracle.com> References: <1435075913-335-1-git-send-email-vkuznets@redhat.com> <1435075913-335-6-git-send-email-vkuznets@redhat.com> <20150710162425.GB24518@l.oracle.com> <87egkcyxy3.fsf@vitty.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZEefL-0008O5-HY for xen-devel@lists.xenproject.org; Mon, 13 Jul 2015 14:25:07 +0000 Content-Disposition: inline In-Reply-To: <87egkcyxy3.fsf@vitty.brq.redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Vitaly Kuznetsov Cc: Wei Liu , Andrew Jones , Keir Fraser , Ian Campbell , Stefano Stabellini , Andrew Cooper , Julien Grall , Ian Jackson , Olaf Hering , Tim Deegan , David Vrabel , Jan Beulich , xen-devel@lists.xenproject.org, Daniel De Graaf List-Id: xen-devel@lists.xenproject.org On Mon, Jul 13, 2015 at 03:44:04PM +0200, Vitaly Kuznetsov wrote: > Konrad Rzeszutek Wilk writes: > > > On Tue, Jun 23, 2015 at 06:11:47PM +0200, Vitaly Kuznetsov wrote: > >> Log first 10 active grants of a domain. This function is going to be used > >> for soft reset, active grants on this path usually mean misbehaving backends > >> refusing to release their mappings on shutdown. > > > > Is there an particular reason 10 was choosen instead of 42 for example :-) > > > > I was inpired by dump_pageframe_info() :-) Ah! > > > Also the 10 should probably have an #define for it. > > > > Ok, any preferred place/name for such define? I would say just include it at the start of the function (and #undef at the end), and maybe later on (if you want to) do a cleanup patch for this and dump_pageframe_info to be controlled by the same 'too long to display' logic. Which I would say could be a function that : - if 'loglvl=info' is used would do the 10. - if 'loglvl=all', then there is no limit. But that is such a minor thing. > > > Not sure I understand the usage case - except for development uses > > to report on the Xen console? But if that is the case why not > > use the 'g' on the ring console? > > If there is a misbehaving backend and this cases the domain to crash > right after the soft reset 'g' option will not be available and it won't > be clear what caused the domain to crash. Aah, that is good information. Please include that in the commit.