From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH 4/9] KVM: define kvm_bad_pfn statically Date: Thu, 2 Aug 2012 10:15:27 -0300 Message-ID: <20120802131527.GE25344@amt.cnet> References: <5014F053.8020305@linux.vnet.ibm.com> <5014F0E1.4010909@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , LKML , KVM To: Xiao Guangrong Return-path: Content-Disposition: inline In-Reply-To: <5014F0E1.4010909@linux.vnet.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, Jul 29, 2012 at 04:14:25PM +0800, Xiao Guangrong wrote: > Then, remove get_bad_pfn > > Signed-off-by: Xiao Guangrong > --- > include/linux/kvm_host.h | 1 + > virt/kvm/kvm_main.c | 7 +------ > 2 files changed, 2 insertions(+), 6 deletions(-) > > diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h > index 4de56cd..b02203f 100644 > --- a/include/linux/kvm_host.h > +++ b/include/linux/kvm_host.h > @@ -50,6 +50,7 @@ > > #define kvm_fault_pfn (-EFAULT) > #define kvm_hwpoison_pfn (-EHWPOISON) > +#define kvm_bad_pfn (-ENOENT) Remind me what is the guarantee that -Exxx does not clash with a valid pfn number?