lkml.org 
[lkml]   [2015]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 08/11] KVM: implement multiple address spaces


On 20/05/2015 17:46, Radim Krčmář wrote:
> I am a bit worried about the explosion that would happen if we wanted,
> for example, per-VCPU address spaces

Those would be very expensive. If we were to implement relocatable APIC
base, we would have to do it in a different way than with memslots.

> My main issue (orthogonal to layering) is that we don't allow a way to
> let userspace tell us that some slots in different name spaces are the
> same slot. We're losing information that could be useful in the future
> (I can only think of less slot queries for dirty log now).

You're right. On the other hand, I think the ship has sailed the moment
the dirty log was GPA-indexed.

> What I like about your solution is that it fits existing code really
> well, is easily modified if needs change, and that it already exists.

Yes, it does fit existing code really well.

Thanks for the discussion!

Paolo


\
 
 \ /
  Last update: 2015-05-20 20:41    [W:0.182 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site