[lkml]   [2006]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 3/13] KVM: kvm data structures
On Thursday 26 October 2006 19:24, Avi Kivity wrote:
> +struct kvm {
> +       spinlock_t lock; /* protects everything except vcpus */
> +       int nmemslots;
> +       struct kvm_memory_slot memslots[KVM_MEMORY_SLOTS];
> +       struct list_head active_mmu_pages;
> +       struct kvm_vcpu vcpus[KVM_MAX_VCPUS];
> +       int memory_config_version;
> +       int busy;
> +};

Assuming that you move to the host-user == guest-real memory
model, will this data structure still be needed? It would
be really nice if a guest could simply consist of a number
of vcpu structures that happen to be used from threads in the
same process address space, but I find it hard to tell if
that is realistic.

Arnd <><
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-10-27 00:59    [W:0.064 / U:1.536 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site