All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike D. Day" <ncmike@us.ibm.com>
To: Tim Deegan <Tim.Deegan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [RFC] New shadow paging code
Date: Mon, 17 Jul 2006 10:32:08 -0400	[thread overview]
Message-ID: <44BB9F68.8070803@us.ibm.com> (raw)
In-Reply-To: <20060714153907.GJ3328@york.uk.xensource.com>

Tim Deegan wrote:


> Our code must deal differently with all the different combinations of
> shadow modes.  However, we expect that once a guest reaches its target
> paging mode, it will stay in that mode for a long time; and the host will
> never change its paging mode.  Rather than having a whole string of ifs in
> the code based on the current guest and host paging modes, we compile
> different code to deal with each pair of modes (2-on-2, 2-on-3, 2-on-4,
> 3-on-3, 3-on-4, 4-on-4).  (Direct mode is implemented as a special case of
> m-on-m, where m is the host's current paging level.)  While increasing the
> size of the hypervisor overall, this should greatly decrease both the cache
> footprint of the shadow code and reduce pipeline flushes from mispredicted
> branches.

Can you explain how this works? It is not obvious to me from the patch. 
In shadow2.c there is in fact a whole string of #ifs. What mechanism 
causes the file to be multiply compiled? Or do I misunderstand how this 
works?

Also, can you comment on the differences and similarities with the 
shadow code contributed by Ben Thomas?

thanks,

Mike Day

  reply	other threads:[~2006-07-17 14:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 15:39 [RFC] New shadow paging code Tim Deegan
2006-07-17 14:32 ` Mike D. Day [this message]
2006-07-17 15:30   ` Tim Deegan
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14 17:58 Kurtz, Ryan M.
2006-07-17  8:12 ` Tim Deegan
2006-08-01 11:31 ` Tim Deegan
2006-08-08 10:02   ` Tim Deegan
2006-08-11 17:40     ` Tim Deegan
2006-08-11 19:48       ` James Morris
2006-08-12  9:40         ` Tim Deegan
2006-08-13 20:36       ` Puthiyaparambil, Aravindh
2006-08-15 13:24         ` Tim Deegan
2006-08-15 13:29           ` Puthiyaparambil, Aravindh
2006-08-15 15:04           ` Tim Deegan
2006-08-15 15:34             ` Puthiyaparambil, Aravindh
2006-08-16 10:34       ` Tim Deegan
2006-08-17  4:48         ` Puthiyaparambil, Aravindh
2006-08-17  4:59           ` Puthiyaparambil, Aravindh
2006-08-17  7:00             ` Puthiyaparambil, Aravindh
2006-08-17  8:35           ` Tim Deegan
2006-08-17 15:02             ` Puthiyaparambil, Aravindh
2006-08-17 20:54         ` Steve Dobbelstein
2006-08-11 17:56 Nakajima, Jun
2006-08-14  9:21 ` Tim Deegan
2006-08-15  3:51 Yu, Ping Y
2006-08-15 13:13 ` Puthiyaparambil, Aravindh
2006-08-16  3:54 Yu, Ping Y
2006-08-17 13:05 Yu, Ping Y

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=44BB9F68.8070803@us.ibm.com \
    --to=ncmike@us.ibm.com \
    --cc=Tim.Deegan@xensource.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.