[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfaFaSGmrfX+veWf_E3kp7ghRjxmiVQRC=Bmv0Z8stWRrg@mail.gmail.com>
Date: Wed, 17 Apr 2024 23:47:16 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
isaku.yamahata@...el.com, xiaoyao.li@...el.com, binbin.wu@...ux.intel.com,
rick.p.edgecombe@...el.com
Subject: Re: [PATCH 5/7] KVM: x86/mmu: Introduce kvm_tdp_map_page() to
populate guest memory
On Wed, Apr 17, 2024 at 11:34 PM Sean Christopherson <seanjc@...glecom> wrote:
>
> On Wed, Apr 17, 2024, Sean Christopherson wrote:
> > On Wed, Apr 17, 2024, Paolo Bonzini wrote:
> > > + case RET_PF_EMULATE:
> > > + return -EINVAL;
>
> Almost forgot. EINVAL on emulation is weird. I don't know that any return code
> is going to be "good", but I think just about anything is better than EINVAL,
> e.g. arguably this could be -EBUSY since retrying after creating a memslot would
> succeed.
Then I guess -ENOENT?
Paolo
Powered by blists - more mailing lists