From: Kip Macy <kmacy@fsmware.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Christian Limpach <chris@pin.lu>, xen-devel@lists.sourceforge.net
Subject: Re: do_set_gdt
Date: Sun, 29 Feb 2004 19:57:42 -0800 (PST) [thread overview]
Message-ID: <20040229195625.G89683@demos.bsdclusters.com> (raw)
In-Reply-To: <E1AxNIh-00073X-00@wisbech.cl.cam.ac.uk>
That is a nice complete definition. Why don't you paste it into
interface.tex?
-Kip
>
> frame_list: An array of up to 16 page frames within which the GDT
> resides. Any frame registered as a GDT frame may only be mapped
> read-only within the guest's address space (e.g., no writeable
> mappings, no use as a page-table page, and so on).
>
> entries: The number of descriptor-entry slots in the GDT. Note that
> the table must be large enough to contain Xen's reserved entries; thus
> we must have 'entries > LAST_RESERVED_GDT_ENTRY'. Note also that,
> after registering the GDT, slots FIRST_RESERVED_GDT_ENTRY to
> LAST_RESERVED_GDT_ENTRY are no longer usable by the guest and may be
> overwritten by Xen.
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-03-01 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 5:20 do_set_gdt Kip Macy
2004-02-28 14:39 ` do_set_gdt Christian Limpach
2004-02-28 14:44 ` do_set_gdt Keir Fraser
2004-02-28 19:09 ` do_set_gdt Kip Macy
2004-02-28 21:10 ` do_set_gdt Christian Limpach
2004-02-28 22:05 ` do_set_gdt Kip Macy
2004-02-29 0:41 ` do_set_gdt Christian Limpach
2004-02-29 9:31 ` do_set_gdt Keir Fraser
2004-03-01 3:57 ` Kip Macy [this message]
2004-02-29 9:22 ` do_set_gdt Keir Fraser
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=20040229195625.G89683@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=chris@pin.lu \
--cc=xen-devel@lists.sourceforge.net \
/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.