From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] x86-64: make compat_start_thread() match start_thread()
Date: Thu, 08 Oct 2009 19:41:04 -0700 [thread overview]
Message-ID: <1255056064.2638.9.camel@sbs-t61.sc.intel.com> (raw)
In-Reply-To: <4ACE8D51.1080606@zytor.com>
On Thu, 2009-10-08 at 18:09 -0700, H. Peter Anvin wrote:
> diff --git a/arch/x86/kernel/process_64.c
> b/arch/x86/kernel/process_64.c
> index ad535b6..ec223a8 100644
> --- a/arch/x86/kernel/process_64.c
> +++ b/arch/x86/kernel/process_64.c
> @@ -356,7 +356,7 @@ start_thread(struct pt_regs *regs, unsigned long
> new_ip, unsigned long new_sp)
> percpu_write(old_rsp, new_sp);
> regs->cs = __USER_CS;
> regs->ss = __USER_DS;
> - regs->flags = 0x200;
> + regs->flags = X86_EFLAGS_IF;
> set_fs(USER_DS);
> /*
> * Free the old FP and other extended state
> @@ -365,6 +365,27 @@ start_thread(struct pt_regs *regs, unsigned long
> new_ip, unsigned long new_sp)
> }
> EXPORT_SYMBOL_GPL(start_thread);
>
> +#ifdef CONFIG_IA32_EMULATION
> +void compat_start_thread(struct pt_regs *regs, u32 new_ip, u32
> new_sp)
> +{
> + loadsegment(fs, 0);
> + loadsegment(ds, __USER32_DS);
> + loadsegment(es, __USER32_DS);
> + load_gs_index(0);
> + regs->ip = new_ip;
> + regs->sp = new_sp;
> + percpu_write(old_rsp, new_sp);
> + regs->cs = __USER32_CS;
> + regs->ss = __USER32_DS;
> + regs->flags = X86_EFLAGS_IF;
> + set_fs(USER_DS);
> + /*
> + * Free the old FP and other extended state
> + */
> + free_thread_xstate(current);
> +}
> +#endif
> +
Peter, While you are it, we should just merge most of the meat into one
common function handling both modes. That will be more cleaner.
thanks,
suresh
prev parent reply other threads:[~2009-10-09 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 1:09 H. Peter Anvin
2009-10-09 2:41 ` Suresh Siddha [this message]
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=1255056064.2638.9.camel@sbs-t61.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®