public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] ix86: don't waste fixmap entries
@ 2013-05-29 12:22 Jan Beulich
  2013-05-31 12:47 ` [tip:x86/mm] ix86: Don't " tip-bot for Jan Beulich
  0 siblings, 1 reply; 2+ messages in thread
From: Jan Beulich @ 2013-05-29 12:22 UTC (permalink / raw)
  To: mingo, tglx, hpa; +Cc: Marcelo Tosatti, linux-kernel

The vsyscall related pvclock entries can only ever be used on x86-64,
and hence they shouldn't even get allocated for 32-bit kernels (the
more that it is there where address space is relatively precious).

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>

---
 arch/x86/include/asm/fixmap.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- 3.10-rc3/arch/x86/include/asm/fixmap.h
+++ 3.10-rc3-ix86-fixmap-no-pvclock/arch/x86/include/asm/fixmap.h
@@ -81,11 +81,11 @@ enum fixed_addresses {
 			    + ((VSYSCALL_END-VSYSCALL_START) >> PAGE_SHIFT) - 1,
 	VVAR_PAGE,
 	VSYSCALL_HPET,
-#endif
 #ifdef CONFIG_PARAVIRT_CLOCK
 	PVCLOCK_FIXMAP_BEGIN,
 	PVCLOCK_FIXMAP_END = PVCLOCK_FIXMAP_BEGIN+PVCLOCK_VSYSCALL_NR_PAGES-1,
 #endif
+#endif
 	FIX_DBGP_BASE,
 	FIX_EARLYCON_MEM_BASE,
 #ifdef CONFIG_PROVIDE_OHCI1394_DMA_INIT




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-05-31 12:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-29 12:22 [PATCH] ix86: don't waste fixmap entries Jan Beulich
2013-05-31 12:47 ` [tip:x86/mm] ix86: Don't " tip-bot for Jan Beulich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox