From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752555AbbIQPdl (ORCPT ); Thu, 17 Sep 2015 11:33:41 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34918 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103AbbIQPdj (ORCPT ); Thu, 17 Sep 2015 11:33:39 -0400 Subject: Re: [PATCH 0/3] x86/paravirt: Fix baremetal paravirt MSR ops To: Arjan van de Ven , Andy Lutomirski , Ingo Molnar References: <20150917071920.GA14296@gmail.com> <55FADBE6.9040008@linux.intel.com> <55FADC3D.70202@redhat.com> <55FADCBD.4070804@linux.intel.com> Cc: Andy Lutomirski , X86 ML , Peter Zijlstra , KVM list , xen-devel , "linux-kernel@vger.kernel.org" , Linus Torvalds , Thomas Gleixner , Peter Zijlstra , Andrew Morton , "H. Peter Anvin" From: Paolo Bonzini Message-ID: <55FADD4B.601@redhat.com> Date: Thu, 17 Sep 2015 17:33:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55FADCBD.4070804@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/09/2015 17:31, Arjan van de Ven wrote: >> >> What about 0 + WARN? > > why 0? > > 0xdeadbeef or any other pattern (even 0x3636363636) makes more sense (of > course also WARN... but most folks don't read dmesg for WARNs) > > (it's the same thing we do for list or slab poison stuff) Sorry, brain fart. That makes sense for the safe variants. It would require some auditing though. Paolo