From: Michael Vrable <mvrable@cs.ucsd.edu>
To: xen-devel@lists.xensource.com
Subject: Shadow Code Reorganization
Date: Sun, 24 Jul 2005 13:42:27 -0700 [thread overview]
Message-ID: <20050724204227.GA9198@vrable.net> (raw)
I'm trying to understand some of the changes that were made to the
shadow page table code a couple weeks ago to add support for 64-bit
modes: changesets f261f14b9781f949f95a328433eff187c677a70b and
0bcfd66a431ebfc70fc068a134e684568ac02966, committed on July 11.
I'm trying to make sense of what seems to be some code duplication. In
xen/arch/x86, there are three files related to shadow mode: shadow.c,
shadow32.c, and shadow_public.c. In my x86 build, only shadow32.c is
built. shadow.c seems to contain a lot of similar code. The comments
at the top of the files are also confusing; shadow32.c claims that it is
shadow.c, and shadow.c claims that it is shadow_64.c.
The Makefile is not very illuminating; for an x86_64 build, shadow32.o
is not built (not surprising), otherwise, shadow.o, shadow_public.o, and
shadow_xxx.o are skipped (the first two names sound rather generic to
me, and shadow_xxx.o looks like part of a not-quite-finished change).
Can anyone explain how this code is supposed to be structured, what is
supposed to end up in each of the files, and whether the files are still
in need of some renaming (say, shadow.c -> shadow64.c)?
--Michael Vrable
next reply other threads:[~2005-07-24 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 20:42 Michael Vrable [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-24 21:53 Shadow Code Reorganization Ian Pratt
2005-07-26 12:44 ` Gerd Knorr
2005-07-26 21:15 Ian Pratt
2005-07-27 7:27 ` Gerd Knorr
2005-07-27 9:51 Ian Pratt
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=20050724204227.GA9198@vrable.net \
--to=mvrable@cs.ucsd.edu \
--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.