All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Robert Phillips <rsp.vi.xen@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Fwd: Re: [RFC] XI Shadow Page Table Mechanism]
Date: Thu, 22 Jun 2006 09:14:30 -0500	[thread overview]
Message-ID: <449AA5C6.2050108@us.ibm.com> (raw)
In-Reply-To: <fc060d960606220710r66e46f1jc2129cda712089ca@mail.gmail.com>

Robert Phillips wrote:
>
>     This isn't supported currently?  Since an HVM must go through 16
>     bit, 32
>     bit, and 64 bit mode to boot up, how can we start more than one
>     guest at
>     a time currently if this doesn't already work?
>
>
> Ed Smith's daily test results show there have been problems with SMP.  
> We haven't diagnosed these problems but, from reading the pre-XI 
> shadow code, it's not clear how it copes with multiple VCPUs in the 
> same domain running in different modes.

There's only a short period of time when this would be happening right?  
During boot up?

>     - how do you deal with large pages within the hypervisor?  do you
>     coalesce or just hope there is contiguous pages available? 
>
>
> We just hope that contiguous pages are available.  However we allocate 
> pages for the guest in large extents to maximize this likelihood.  In 
> practice this is very effective for guests created soon after boot 
> time.  There may be fragmentation problems later.

Any ideas about how to deal with this long term?  Large page support 
would also be useful for PV domains.  There was a lot of people at the 
last summit that were interested in this...

Thanks for the responses,

Anthony Liguori

>     - what is the performance benefit in saving the shadow pages for each
>     domain?  there's clearly a memory trade-off here so understanding the
>     performance gain seems important.
>
>
> The performance benefit appears to be substantial but we have not done 
> a thorough study yet.
>
>     - OOM can be dealt with in the existing code by just invalidating
>     existing mappings to free up pages.  what advantages do your approach
>     have to this?  (i realize we don't do this today but in theory, we
>     could).
>
>
> Ultimately XI deals with OOM  by tearing down cached shadow pages, 
> just as you say.  But it uses LRU to pick the victims.
>
>     Interesting stuff.  I'm eager to see the code.
>
>     Regards,
>
>     Anthony Liguori
>
>     > Thanks,
>     > -b
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Xen-devel mailing list
>     > Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
>     > http://lists.xensource.com/xen-devel
>
>
>     --
>     ------------------------------------------------------------------------
>     Ben Thomas                                         Virtual Iron
>     Software
>     bthomas@virtualiron.com
>     <mailto:bthomas@virtualiron.com>                            Tower
>     1, Floor 2
>     978-849-1214                                       900 Chelmsford
>     Street
>                                                         Lowell, MA 01851
>
> ------------------------------------------------------------------------
> Robert S. Phillips                          Virtual Iron Software
> rsp.vi.xen@virtualiron.com 
> <mailto:rsp.vi.xen@virtualiron.com>             Tower 1, Floor 2
> 978-849-1220                                 900 Chelmsford Street
>                                                     Lowell, MA 01851 

      reply	other threads:[~2006-06-22 14:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <449A9BD5.5030703@virtualiron.com>
2006-06-22 14:10 ` [Fwd: Re: [RFC] XI Shadow Page Table Mechanism] Robert Phillips
2006-06-22 14:14   ` Anthony Liguori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=449AA5C6.2050108@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=rsp.vi.xen@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.