mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander van Heukelum <heukelum@fastmail.fm>
To: Andy Lutomirski <luto@amacapital.net>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Oleg Nesterov <oleg@redhat.com>, Borislav Petkov <bp@suse.de>,
	Rik van Riel <riel@redhat.com>
Subject: [PATCHv2 0/4] x86, entry: some cleanup and simplification...
Date: Sun, 18 Jan 2015 12:45:16 +0100	[thread overview]
Message-ID: <1421581520-2816-1-git-send-email-heukelum@fastmail.fm> (raw)

Hi Andy,

The last patchset did not compile on i386. Please ignore it. This one
should be better. Instead of removing KERNEL_STACK_OFFSET, it is now
used consistently on both i386 and x86_64.

Boot tested using qemu (using klibc for userspace)
	- x86_64, 32-bit userspace, core2duo (sysenter32)
	- x86_64, 32-bit userspace, phenom (syscall32)
	- x86_64, 32-bit userspace, vdso=0 (int 0x80)
	- x86_64, 64-bit userspace
	- i386, pentium3 (sysenter)
	- i386, athlon (syscall)
	- i386, vdso=0 (int 0x80)

They were tested on top of 22f2aa4a0361707a5cfb1de9d45260b39965dead
(x86/entry-devel in your tree) and this kernel is now running on my
laptop.

Greetings,
   Alexander

Alexander van Heukelum (4):
  x86_64: cleanup THREAD_INFO(reg,offset) macro
  x86_64: embrace KERNEL_STACK_OFFSET
  i386: clean up KERNEL_STACK_OFFSET
  x86_64, entry: Create IRET-compatible stack frame at syscall entry

 arch/x86/ia32/ia32entry.S          | 33 ++++++++--------
 arch/x86/include/asm/calling.h     |  1 +
 arch/x86/include/asm/processor.h   | 43 ++++++++-------------
 arch/x86/include/asm/thread_info.h | 17 +++++++-
 arch/x86/kernel/entry_32.S         |  5 ++-
 arch/x86/kernel/entry_64.S         | 79 +++++++++++---------------------------
 arch/x86/kernel/process_64.c       |  5 +--
 7 files changed, 75 insertions(+), 108 deletions(-)

-- 
2.1.0


             reply	other threads:[~2015-01-18 11:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 11:45 Alexander van Heukelum [this message]
2015-01-18 11:45 ` [PATCHv2 1/4] x86_64: cleanup THREAD_INFO(reg,offset) macro Alexander van Heukelum
2015-01-21 13:40   ` Denys Vlasenko
2015-01-21 16:20     ` Alexander van Heukelum
2015-01-21 18:04       ` Borislav Petkov
2015-01-21 18:48         ` Alexander van Heukelum
2015-01-18 11:45 ` [PATCHv2 2/4] x86_64: embrace KERNEL_STACK_OFFSET Alexander van Heukelum
2015-01-21 13:44   ` Denys Vlasenko
2015-01-21 16:29     ` Alexander van Heukelum
2015-01-23  0:53       ` Denys Vlasenko
2015-01-18 11:45 ` [PATCHv2 3/4] i386: clean up KERNEL_STACK_OFFSET Alexander van Heukelum
2015-01-18 11:45 ` [PATCHv2 4/4] x86_64, entry: Create IRET-compatible stack frame at syscall entry Alexander van Heukelum
2015-01-18 16:38   ` Andy Lutomirski
2015-01-18 17:22     ` Alexander van Heukelum
2015-01-18 12:05 ` [PATCHv2 0/4] x86, entry: some cleanup and simplification Borislav Petkov
2015-01-18 15:47   ` Alexander van Heukelum
2015-01-21 13:26     ` Denys Vlasenko
2015-01-21 15:51       ` Alexander van Heukelum

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=1421581520-2816-1-git-send-email-heukelum@fastmail.fm \
    --to=heukelum@fastmail.fm \
    --cc=bp@suse.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.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

all inboxes | Powered by JetHome®