From: Chris Lalancette <clalance@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: 32-on-64 support in xen-unstable?
Date: Mon, 06 Jul 2009 16:18:25 +0200 [thread overview]
Message-ID: <4A5207B1.3030808@redhat.com> (raw)
Hello,
I've been browsing through the preemptible pagetable stuff, and ran across
a piece of code that I don't understand or is buggy. Looking at
arch/x86/mm.c:new_guest_cr3(), we have this code for 32-on-64 support:
if ( is_pv_32on64_domain(d) )
{
okay = paging_mode_refcounts(d)
? 0 /* Old code was broken, but what should it be? */
: mod_l4_entry(
__va(pagetable_get_paddr(curr->arch.guest_table)),
l4e_from_pfn(
mfn,
(_PAGE_PRESENT|_PAGE_RW|_PAGE_USER|_PAGE_ACCESSED)),
pagetable_get_pfn(curr->arch.guest_table), 0, 0, curr) == 0;
if ( unlikely(!okay) )
{
MEM_LOG("Error while installing new compat baseptr %lx", mfn);
return 0;
}
However, looking at arch/x86/mm.c:mod_l4_entry(), it returns 0 on success and <
0 on error. It seems to me that booting a 32-bit PV guest is always going to
fall into the !okay check on success, when it really shouldn't. Shouldn't this
be something like:
okay = paging_mode_refcounts(d)
? 0 /* Old code was broken, but what should it be? */
: !mod_l4_entry(
__va(pagetable_get_paddr(curr->arch.guest_table)),
l4e_from_pfn(
mfn,
(_PAGE_PRESENT|_PAGE_RW|_PAGE_USER|_PAGE_ACCESSED)),
pagetable_get_pfn(curr->arch.guest_table), 0, 0, curr) == 0;
Or am I just missing something? (NOTE: this still leaves open the possibility
for failure if mod_l4_entry() returns EINTR or EAGAIN, but maybe we don't have
to worry about that here?)
Thanks,
--
Chris Lalancette
next reply other threads:[~2009-07-06 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 14:18 Chris Lalancette [this message]
2009-07-06 14:37 ` 32-on-64 support in xen-unstable? Jan Beulich
2009-07-06 14:44 ` Chris Lalancette
2009-07-06 15:23 ` 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=4A5207B1.3030808@redhat.com \
--to=clalance@redhat.com \
--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.