From: Hollis Blanchard <hollisb@us.ibm.com>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-ppc-devel@lists.xensource.com, xen-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com
Subject: Re: Linux PG_arch_1 conflict
Date: Fri, 10 Mar 2006 14:59:10 -0600 [thread overview]
Message-ID: <4411E89E.9090101@us.ibm.com> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD59FF3C2@cacexc12.americas.cpqcorp.net>
Magenheimer, Dan (HP Labs Fort Collins) wrote:
> See previous discussion at:
>
> http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00238.html
>
>
> The issue is that PG_arch_1 is reserved for arch-specific
> usage, the paravirtualization changes for Xenlinux utilize
> it (to mark foreign pages) because it was otherwise unused
> in Linux/x86. But Xen is no longer an arch.
>
> Grep'ing for "PageForeign" in -sparse will show most (all?)
> of the actual uses of it. Nearly all are in x86-specific
> code. But one is in netback_init().
That thread seems to already have a solution. Has anybody run it past
Linux MM people? (Adding xen-devel to CC for greater exposure.)
--
Hollis Blanchard
IBM Linux Technology Center
next parent reply other threads:[~2006-03-10 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <516F50407E01324991DD6D07B0531AD59FF3C2@cacexc12.americas.cpqcorp.net>
2006-03-10 20:59 ` Hollis Blanchard [this message]
2006-03-10 21:11 Linux PG_arch_1 conflict Magenheimer, Dan (HP Labs Fort Collins)
2006-03-11 9:31 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 21:20 Magenheimer, Dan (HP Labs Fort Collins)
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=4411E89E.9090101@us.ibm.com \
--to=hollisb@us.ibm.com \
--cc=dan.magenheimer@hp.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-ppc-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.