From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753311AbbETJAD (ORCPT ); Wed, 20 May 2015 05:00:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55215 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753269AbbETI77 (ORCPT ); Wed, 20 May 2015 04:59:59 -0400 Message-ID: <555C4CA1.3080704@redhat.com> Date: Wed, 20 May 2015 10:58:09 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Christian Borntraeger , linux-kernel@vger.kernel.org, kvm@vger.kernel.org CC: Xiao Guangrong , rkrcmar@redhat.com, bdas@redhat.com, linux-s390 Subject: Re: [RFC PATCH 00/11] KVM: multiple address spaces (for SMM) References: <1431956923-35602-1-git-send-email-pbonzini@redhat.com> <555C467E.5060106@de.ibm.com> In-Reply-To: <555C467E.5060106@de.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/05/2015 10:31, Christian Borntraeger wrote: > > So in essence this allows to have each vcpu in separate address space if > necessary. These address space might overlap or be identical and allow > permutations by having different memslots for each address space. > And we can have several address spaces per vcpu. Correct? Yes, exactly. I've also posted QEMU patches that may give more insight on how this is used. Paolo > This might be useful for kvm on s390 (e.g. we did the ucontrol thing that > also has one guest address space per vcpu). I need to have a look at that.