[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140530073323.GB28131@pd.tnic>
Date: Fri, 30 May 2014 09:33:23 +0200
From: Borislav Petkov <bp@...en8.de>
To: Dave Young <dyoung@...hat.com>
Cc: Vivek Goyal <vgoyal@...hat.com>, matt.fleming@...el.com,
linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org
Subject: Re: [PATCH] export efi.flags to sysfs
On Fri, May 30, 2014 at 10:24:38AM +0800, Dave Young wrote:
> > > > How does /sys/firmware/efi/runtime-map/* look like with old mapping? Can't
> > > > we look at it and figure out if it is 1:1 or not.
> > >
> > > There's phys_addr and virt_addr, (virt_addr - phys_addr) will always be
> > > -64G for 1:1 map, ioremapped addresses space is different.
>
> Correct myself it's top to down (-4G - -64G) instead of down to top.
This is the new mapping.
AFAICR, the question is about the old mapping. Which was "normal"
ioremap into the kernel page table. The new mapping is into another page
table.
> > I am curious that what's the meaning of 1:1 mapping here? So far I thought
> > that means virt and physical addresses are same but that does not seem
> > to be the case. So what does it mean?
>
> while doing the mapping, we will iterate the memory ranges (md[])
>
> Like below without considering alignment:
> Virt addr (down) <------------------------------> (top)
> md0 (size0) <----->
> (size0)
> md1 (size1) <------->
> (size1)
> ...
>
> Boris can correct me if I'm wrong.
Yes, this is the new mapping, top = -2G.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists