From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Stephen Tweedie <sct@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Mark McLoughlin <markmc@redhat.com>,
x86@kernel.org
Subject: [PATCH 0 of 8] x86/xen: updated physical mapping patches, and _PAGE_GLOBAL cleanup
Date: Tue, 01 Jul 2008 16:46:29 -0700 [thread overview]
Message-ID: <patchbomb.1214955989@localhost> (raw)
Hi Ingo,
Here's a revised series of the Xen-64 groundwork patches relating to
creating the physical memory mapping. The first few patches are the
necessary changes to make it work without triggering CPA warnings, and
the last couple are cleanups of _PAGE_GLOBAL in the _PAGE_KERNEL
flags, and could probably happily live in another topic branch
(they're not at all Xen-specific or required for Xen to work).
Breakdown:
1 - x86_64: create global mappings in head_64.S
Create global mappings in head_64.S for consistency,
to avoid spurious CPA failures.
2-5: Map physical memory in a Xen-compatible way
These superscede "x86, 64-bit: adjust mapping of physical pagetables
to work with Xen".
6: Fold _PAGE_GLOBAL into _PAGE_KENREL mappings
This reverts patch 1, by solving the problem in a more general way.
7: Remove __PAGE_KERNEL* from 32-bit
Patch 7 makes the 32-bit kernel's __PAGE_KERNEL variables redundant,
so remove them.
8: Make CPA testing use some other pte bit
Use an unused bit to test CPA, rather than _PAGE_GLOBAL, so that
testing will still work when _PAGE_GLOBAL isn't usable.
Thanks,
J
next reply other threads:[~2008-07-02 1:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 23:46 Jeremy Fitzhardinge [this message]
2008-07-01 23:46 ` [PATCH 1 of 8] x86_64: create global mappings in head_64.S Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 2 of 8] x86_64: unmap iomapping before populating Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 3 of 8] x86_64/setup: preserve existing PUD mappings Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 4 of 8] x86_64/setup: unconditionally populate the pgd Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 5 of 8] x86_64/setup: create 4k mappings if the cpu doens't support PSE Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 6 of 8] x86: always set _PAGE_GLOBAL in _PAGE_KERNEL* flags Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 7 of 8] x86_32: remove __PAGE_KERNEL(_EXEC) Jeremy Fitzhardinge
2008-07-01 23:46 ` [PATCH 8 of 8] x86/cpa: use an undefined PTE bit for testing CPA Jeremy Fitzhardinge
2008-07-04 10:33 ` [PATCH 0 of 8] x86/xen: updated physical mapping patches, and _PAGE_GLOBAL cleanup Ingo Molnar
2008-07-04 15:56 ` Jeremy Fitzhardinge
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=patchbomb.1214955989@localhost \
--to=jeremy@goop.org \
--cc=ehabkost@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mingo@elte.hu \
--cc=sct@redhat.com \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox