From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5 00/13] KVM/X86: Introduce a new guest mapping interface
Date: Thu, 31 Jan 2019 14:10:23 +0100
Message-ID: <725d97e1-d95a-b243-ac6f-c62768fd7cf6@redhat.com>
References: <1547026933-31226-1-git-send-email-karahmed@amazon.de>
 <20190123181636.GR19289@Konrads-MacBook-Pro.local>
 <1548440932.17444.29.camel@amazon.de>
 <72d9954b-37f8-3f39-37f7-b292766da480@redhat.com>
 <1548939805.28936.9.camel@amazon.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
        "rkrcmar@redhat.com" <rkrcmar@redhat.com>
To: "Raslan, KarimAllah" <karahmed@amazon.de>,
        "konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <1548939805.28936.9.camel@amazon.de>
Content-Language: en-US
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 31/01/19 14:03, Raslan, KarimAllah wrote:
> 
> One option here would be to add 'e820__mapped_raw_any' (or whatever 
> other name) and make it identical to the current implementation of 
> e820__mapped_any at. Would that be slightly more acceptable? :)

Yes, of course it would (for me at least :)).

Paolo