From: Rik van Riel <riel@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: invalid PTE for xen_start-info ?
Date: Wed, 04 Oct 2006 09:47:15 -0400 [thread overview]
Message-ID: <4523BB63.5000005@redhat.com> (raw)
In-Reply-To: <C1492AA0.2088%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 3/10/06 7:06 pm, "Rik van Riel" <riel@redhat.com> wrote:
>
>> pte 0000000019800027 (real 0010000035010027)
>>
>> That last PTE value does not look like a valid x86-64 PTE
>> value to me. That high bit is not the NX bit, nor is it
>> within the physical address range of the system in question.
>>
>> What's going on here?
>>
>> Is this a bug you would like a fix for?
>
> It's not a bug -- it's one of the available-for-software flags that is
> stolen by Xen to indicate a kernel PTE. This is done so that we can
> distinguish kernel and user mappings, so that the latter can have the global
> bit set. Sounds weird, but it avoids flushing user mappings from the TLB
> when executing syscalls (we have to change %cr3 value when switching between
> guest-user and guest-kernel modes).
OK, so pte_val() just needs to know about these software flags
and mask them out before passing the value to mfn_to_pfn ?
--
"You don't have to be crazy to do this... but it helps." -- Bob Ross
next prev parent reply other threads:[~2006-10-04 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 10:33 Xen 3.0.3 rc2 available Keir Fraser
2006-10-03 18:06 ` invalid PTE for xen_start-info ? Rik van Riel
2006-10-04 8:08 ` Keir Fraser
2006-10-04 13:47 ` Rik van Riel [this message]
2006-10-04 14:16 ` Keir Fraser
2006-10-04 15:06 ` Rik van Riel
2006-10-04 15:10 ` Keir Fraser
2006-10-03 18:17 ` xen-3.0.3-testing-install-x86_32 dom0 boot failure Richard Miller
2006-10-04 13:46 ` [PATCH] redundant ampersand before array name in __RING_SIZE macro Richard Miller
2006-10-06 20:47 ` Xen 3.0.3 rc2 available Nick Craig-Wood
2006-10-06 20:55 ` Anthony Liguori
2006-10-09 8:46 ` Nick Craig-Wood
2006-10-06 22:44 ` 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=4523BB63.5000005@redhat.com \
--to=riel@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.