From: Jiri Slaby <jirislaby@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86: clean up use of system_state in virt_addr_valid and co
Date: Thu, 05 Mar 2009 23:05:50 +0100 [thread overview]
Message-ID: <49B04CBE.9080308@gmail.com> (raw)
In-Reply-To: <49AF35B0.2000302@goop.org>
On 5.3.2009 03:15, Jeremy Fitzhardinge wrote:
> 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
Looks good, thanks. Just an idea, wouldn't make sense to add the check
directly into is_vmalloc_addr?
next prev parent reply other threads:[~2009-03-05 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 2:15 [GIT PULL] x86: clean up use of system_state in virt_addr_valid and co Jeremy Fitzhardinge
2009-03-05 13:59 ` Ingo Molnar
2009-03-05 22:05 ` Jiri Slaby [this message]
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=49B04CBE.9080308@gmail.com \
--to=jirislaby@gmail.com \
--cc=jeremy@goop.org \
--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