|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] odd gfn number checking in p2m.c
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] odd gfn number checking in p2m.c,
Olaf Hering <=
|
|
|
|
|