mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/5] x86-64, docs, mm: Add vsyscall range to virtual address space layout
Date: Mon, 4 Mar 2013 22:56:39 +0100	[thread overview]
Message-ID: <20130304215639.GH22274@pd.tnic> (raw)
In-Reply-To: <513515F0.7050603@mit.edu>

On Mon, Mar 04, 2013 at 01:45:20PM -0800, Andy Lutomirski wrote:
> vsyscalls are only 4k.  Am I missing something obvious her?

Right, but we're reserving 5 level2 pages for this, i.e. 5*512*4K = 10M.
I.e., each level2 page contains 512 ptes, each pointing to a 4K page.

arch/x86/kernel/head_64.S:

...
NEXT_PAGE(level2_fixmap_pgt)
	.fill	506,8,0
	.quad	level1_fixmap_pgt - __START_KERNEL_map + _PAGE_TABLE
	/* 8MB reserved for vsyscalls + a 2MB hole = 4 + 1 entries */
	.fill	5,8,0

NEXT_PAGE(level1_fixmap_pgt)
	.fill	512,8,0

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-03-04 21:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 20:16 [PATCH 0/5] x86: Misc fixlets Borislav Petkov
2013-03-04 20:16 ` [PATCH 1/5] x86, smpboot: Remove unused variable Borislav Petkov
2013-03-06  0:24   ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 2/5] x86: Drop KERNEL_IMAGE_START Borislav Petkov
2013-04-03  0:18   ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 3/5] x86-64, docs, mm: Add vsyscall range to virtual address space layout Borislav Petkov
2013-03-04 21:45   ` Andy Lutomirski
2013-03-04 21:56     ` Borislav Petkov [this message]
2013-04-03  0:19   ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 4/5] x86, msr: Unify variable names Borislav Petkov
2013-04-03  0:20   ` [tip:x86/cleanups] " tip-bot for Borislav Petkov
2013-03-04 20:16 ` [PATCH 5/5] x86, quirks: Shut-up a long-standing gcc warning Borislav Petkov
2013-04-03  0:21   ` [tip:x86/cleanups] " tip-bot for Borislav Petkov

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=20130304215639.GH22274@pd.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --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

all inboxes | Powered by JetHome®