public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Jiri Slaby <jirislaby@gmail.com>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86: clean up use of system_state in virt_addr_valid and co
Date: Wed, 04 Mar 2009 18:15:12 -0800	[thread overview]
Message-ID: <49AF35B0.2000302@goop.org> (raw)

These two changes remove the tests based on system_state in the virt_addr_valid/phys_addr functions.
It replaces the i386 test with an explicit flag to indicate whether the vmalloc range has been determined,
and on x86-64, it pre-initializes the x86_phys_bits to a reasonable number so that there's no dependency
on init order.

	J

The following changes since commit 4d02f9f7dac27f801fed69be8ebb0b95b798b12c:
  Ingo Molnar (1):
        Merge branch 'x86/urgent'

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git x86/virt

Jeremy Fitzhardinge (2):
      x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid
      x86-64: pre-initialize boot_cpu_data.x86_phys_bits to avoid system_state tests

 arch/x86/include/asm/pgtable_32_types.h |    5 +++++
 arch/x86/kernel/setup.c                 |    4 +++-
 arch/x86/mm/init_32.c                   |    3 +++
 arch/x86/mm/ioremap.c                   |   14 +++++---------
 4 files changed, 16 insertions(+), 10 deletions(-)



             reply	other threads:[~2009-03-05  2:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  2:15 Jeremy Fitzhardinge [this message]
2009-03-05 13:59 ` [GIT PULL] x86: clean up use of system_state in virt_addr_valid and co Ingo Molnar
2009-03-05 22:05 ` Jiri Slaby
2009-03-05 22:57   ` 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=49AF35B0.2000302@goop.org \
    --to=jeremy@goop.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vegard.nossum@gmail.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