linux-kernel - Re: [RFC PATCH 00/11] KVM: multiple address spaces (for SMM)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 May 2015 10:58:09 +0200
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Christian Borntraeger <borntraeger@...ibm.com>,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
CC:	Xiao Guangrong <guangrong.xiao@...ux.intel.com>,
	rkrcmar@...hat.com, bdas@...hat.com,
	linux-s390 <linux-s390@...r.kernel.org>
Subject: Re: [RFC PATCH 00/11] KVM: multiple address spaces (for SMM)



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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/