From: Jacob Gorm Hansen <jacob@melon.dk>
To: Xen list <xen-devel@lists.sourceforge.net>
Subject: Failure in update_l1e()
Date: Tue, 13 Apr 2004 15:00:59 +0200 [thread overview]
Message-ID: <1081861258.15566.108.camel@jacobg> (raw)
hi,
I am seeing occasional failures of cmpxchg_user() in update_l1e().
According to the the comments in the source, this is due to a page fault
caused by the update.
The error looks like this:
(XEN) DOM5: (file=memory.c, line=670) Failed to update 08fe6065 ->
08fe6465: saw 08fe6065
DOM5: Failed update VA mapping: 000bffff, 08fe6465, 00000002
The odd value is due to a special use of one of the AVL bits for my own
purposes.
This only happens when page_nr is 000bffff for some reason.
Any ideas what may be going wrong here?
thanks,
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-04-13 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 13:00 Jacob Gorm Hansen [this message]
2004-04-13 13:47 ` Failure in update_l1e() 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=1081861258.15566.108.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.