All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
	venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: ACPI early ioremap problems
Date: Sat, 19 Jan 2008 20:16:21 +0100	[thread overview]
Message-ID: <20080119191621.GA3865@one.firstfloor.org> (raw)
In-Reply-To: <20080119184543.GA3751@elte.hu>

> hm, so are you saying that on 64-bit there's in essence no usable 
> ioremap facility between zap_low_mappings() and paging_init()? 
> (early_ioremap() is not usable anymore, and ioremap() is not yet 
> usable.) I guess we'll have to pick up the 32-bit early_ioremap() code 
> for 64-bit as well.

No early_ioremap() should work. Or rather used to work. 

It does map into the kernel mapping which is not zapped. It just broke 
recently.

But it definitely used to work because several users used it before
paging_init() even before the recent PAT changes.

-Andi

  reply	other threads:[~2008-01-19 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080119030843.GA2028@basil.nowhere.org>
     [not found] ` <20080119150328.GA32370@elte.hu>
     [not found]   ` <20080119152649.GA1375@one.firstfloor.org>
2008-01-19 15:30     ` ACPI early ioremap problems Ingo Molnar
2008-01-19 15:46       ` Andi Kleen
2008-01-19 18:45         ` Ingo Molnar
2008-01-19 19:16           ` Andi Kleen [this message]
2008-01-20 16:48             ` ACPI early ioremap problems II Andi Kleen
2008-01-20 23:50               ` Ingo Molnar
2008-01-21  2:59                 ` Andi Kleen

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=20080119191621.GA3865@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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.