From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xensource.com
Subject: odd gfn number checking in p2m.c
Date: Sun, 19 Sep 2010 17:49:03 +0200 [thread overview]
Message-ID: <20100919154903.GA32635@aepfle.de> (raw)
Hello,
how can a gfn become 0x555555 as checked in
p2m.c:guest_physmap_add_entry() and p2m_alloc_table()?
Looking further in p2m.c, audit_p2m() checks only for a 32bit value.
So where is that magic number set, and why is it not a define to
simplify grepping for users of that value?
Olaf
next reply other threads:[~2010-09-19 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 15:49 Olaf Hering [this message]
2010-09-19 16:41 ` odd gfn number checking in p2m.c 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=20100919154903.GA32635@aepfle.de \
--to=olaf@aepfle.de \
--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.