[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] RE: Co-scheduling HVM domains...


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Roger Cruz" <rcruz@xxxxxxxxxxxxxxxxxxxxxxxx>
  • Date: Wed, 28 Mar 2007 12:05:16 -0400
  • Delivery-date: Wed, 28 Mar 2007 09:04:18 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcdwEslRdy6dEOdyQ7Km6kAAV+zl4AAnNNPQABpkAzAADjDPsA==
  • Thread-topic: [Xen-users] RE: Co-scheduling HVM domains...

>> 1) I've heard of something called stub domains that may do something
>> similar to case 1.  I'm trying to get more info on it.  Don't 
>> know if it
>> even works for Windows HVMs.

> Stub domains has nothing to do with the problem you're trying to
solve. 

My limited understanding of stubs domains is that it allows a
mini-domain to be scheduled with the main domain as a pair.  The
mini-domain would have easy access to the domain's memory space.  So
they are basically two CPU contexts using the same page tables, etc.
That is all I know so far since the info on this is rather limited.


On the issue of the scheduler, I would agree with you on making
"bonding" of domains generic so it can be accepted.

I just wanted to get these questions out there to make sure I was not
missing something obvious or support coming in a near-future release.

Javier,

You asked about whether we have gotten domains to shared memory and the
answer is not yet. We have not even tried.  Our understanding is that
there are grant tables that are supposed to do this and the code is
available for HVM domains as well.  If someone has more accurate info,
please correct my understanding.

Thank you all.
R.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.