From: Jacob Gorm Hansen <jacob@melon.dk>
To: Xen list <xen-devel@lists.sourceforge.net>
Subject: Pagetable updates
Date: Thu, 19 Feb 2004 18:16:57 +0100 [thread overview]
Message-ID: <1077211017.20632.13.camel@jacobg> (raw)
hi,
I am having a problem with some pagetable-updates that seem to by
sneaking past my checks in XenoLinux. I have #undeffed CONFIG_XENO in
mm/memory.c, and have checking code in place in the functions
MULTICALL_flush_page_update_queue() &
__flush_page_update_queue()
in arch/xeno/mm/hypervisor.c.
Is there anywhere else (like in asm-code somewhere) pte-updates are
passed up to Xen without my knowledge?
thanks,
Jacob
-------------------------------------------------------
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 reply other threads:[~2004-02-19 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 17:16 Jacob Gorm Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 17:16 Pagetable updates Jacob Gorm Hansen
2004-02-19 17:24 ` Keir Fraser
2004-02-21 4:13 ` Kip Macy
2004-02-21 4:34 ` Kip Macy
2004-02-21 8:26 ` 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=1077211017.20632.13.camel@jacobg \
--to=jacob@melon.dk \
--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.