linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] use EFLAGS #defines instead of inline constants
Date: Mon, 05 Apr 2004 19:44:04 -0400	[thread overview]
Message-ID: <4071EF44.7090006@quark.didntduck.org> (raw)
In-Reply-To: <20040405160745.3f21f9c3.rddunlap@osdl.org>

Randy.Dunlap wrote:
> // linux-2.6.5
> // use x86 EFLAGS defines in place of inline constants;
> 
> diffstat:=
>  arch/i386/kernel/doublefault.c |    3 ++-
>  arch/i386/kernel/process.c     |    2 +-
>  arch/i386/kernel/signal.c      |    7 ++++++-
>  3 files changed, 9 insertions(+), 3 deletions(-)
> 
> 
> diff -Naurp ./arch/i386/kernel/doublefault.c~use_eflags ./arch/i386/kernel/doublefault.c
> --- ./arch/i386/kernel/doublefault.c~use_eflags	2004-03-10 18:55:22.000000000 -0800
> +++ ./arch/i386/kernel/doublefault.c	2004-04-01 21:10:04.000000000 -0800
> @@ -6,6 +6,7 @@
>  
>  #include <asm/uaccess.h>
>  #include <asm/pgtable.h>
> +#include <asm/processor.h>
>  #include <asm/desc.h>
>  
>  #define DOUBLEFAULT_STACKSIZE (1024)
> @@ -53,7 +54,7 @@ struct tss_struct doublefault_tss __cach
>  	.io_bitmap_base	= INVALID_IO_BITMAP_OFFSET,
>  
>  	.eip		= (unsigned long) doublefault_fn,
> -	.eflags		= 0x00000082,
> +	.eflags		= X86_EFLAGS_SF | 0x2,	/* 0x2 bit is always set */
>  	.esp		= STACK_START,
>  	.es		= __USER_DS,
>  	.cs		= __KERNEL_CS,
> diff -Naurp ./arch/i386/kernel/process.c~use_eflags ./arch/i386/kernel/process.c
> --- ./arch/i386/kernel/process.c~use_eflags	2004-03-30 17:41:30.000000000 -0800
> +++ ./arch/i386/kernel/process.c	2004-04-01 21:10:56.000000000 -0800
> @@ -278,7 +278,7 @@ int kernel_thread(int (*fn)(void *), voi
>  	regs.orig_eax = -1;
>  	regs.eip = (unsigned long) kernel_thread_helper;
>  	regs.xcs = __KERNEL_CS;
> -	regs.eflags = 0x286;
> +	regs.eflags = X86_EFLAGS_IF | X86_EFLAGS_SF | X86_EFLAGS_PF | 0x2;
>  
>  	/* Ok, create the new process.. */
>  	return do_fork(flags | CLONE_VM | CLONE_UNTRACED, 0, &regs, 0, NULL, NULL);
> diff -Naurp ./arch/i386/kernel/signal.c~use_eflags ./arch/i386/kernel/signal.c
> --- ./arch/i386/kernel/signal.c~use_eflags	2004-03-10 18:55:26.000000000 -0800
> +++ ./arch/i386/kernel/signal.c	2004-04-01 21:19:14.000000000 -0800
> @@ -20,6 +20,7 @@
>  #include <linux/personality.h>
>  #include <linux/suspend.h>
>  #include <linux/elf.h>
> +#include <asm/processor.h>
>  #include <asm/ucontext.h>
>  #include <asm/uaccess.h>
>  #include <asm/i387.h>
> @@ -152,6 +153,10 @@ restore_sigcontext(struct pt_regs *regs,
>  	  err |= __get_user(tmp, &sc->seg);				\
>  	  loadsegment(seg,tmp); }
>  
> +#define	FIX_EFLAGS	(X86_EFLAGS_AC | X86_EFLAGS_OF | X86_EFLAGS_DF | \
> +			 X86_EFLAGS_TF | X86_EFLAGS_SF | X86_EFLAGS_ZF | \
> +			 X86_EFLAGS_AF | X86_EFLAGS_PF | X86_EFLAGS_CF)
> +
>  	GET_SEG(gs);
>  	GET_SEG(fs);
>  	COPY_SEG(es);
> @@ -170,7 +175,7 @@ restore_sigcontext(struct pt_regs *regs,
>  	{
>  		unsigned int tmpflags;
>  		err |= __get_user(tmpflags, &sc->eflags);
> -		regs->eflags = (regs->eflags & ~0x40DD5) | (tmpflags & 0x40DD5);
> +		regs->eflags = (regs->eflags & ~FIX_EFLAGS) | (tmpflags & FIX_EFLAGS);
>  		regs->orig_eax = -1;		/* disable syscall checks */
>  	}
>  
> 
> 
> --
> ~Randy

kernel_thread() doesn't really needs PF and SF.  They are just result 
flags that nothing should depend on.  Some additional suggestions are 
cleanup the vm86 code to use the defines from processor.h instead of its 
own, and moving FIX_EFLAGS to processor.h (rename it X86_EFLAGS_USER or 
something).

--
				Brian Gerst

  reply	other threads:[~2004-04-05 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 23:07 [PATCH] use EFLAGS #defines instead of inline constants Randy.Dunlap
2004-04-05 23:44 ` Brian Gerst [this message]
     [not found] <20040405170419.1f2fc143.rddunlap@osdl.org>
2004-04-07  5:46 ` Randy.Dunlap

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=4071EF44.7090006@quark.didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).