mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Ashok Raj <ashok.raj@intel.com>,
	ergot86@gmail.com, torvalds@osdl.org, mingo@elte.hu,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.15] i386: allow disabling X86_FEATURE_SEP at boot
Date: Sat, 28 Jan 2006 01:04:16 -0500	[thread overview]
Message-ID: <200601280106_MC3-1-B6F2-9A79@compuserve.com> (raw)

In-Reply-To: <20060127143713.2efc16ed.akpm@osdl.org>

On Fri, 27 Jan 2006 at 14:37:13 -0800, Andrew Morton wrote:

> Chuck Ebbert <76306.1226@compuserve.com> wrote:
> >
> > Allow the x86 "sep" feature to be disabled at bootup.  This
> > forces use of the int80 vsyscall.
> > 
>
> Why is there a need to do this?

Mainly for testing or benchmarking the int80 vsyscall code.

> > --- 2.6.15a.orig/arch/i386/kernel/cpu/common.c
> > +++ 2.6.15a/arch/i386/kernel/cpu/common.c
> > @@ -27,6 +27,7 @@ EXPORT_PER_CPU_SYMBOL(cpu_16bit_stack);
> >  static int cachesize_override __devinitdata = -1;
> >  static int disable_x86_fxsr __devinitdata = 0;
> >  static int disable_x86_serial_nr __devinitdata = 1;
> > +static int disable_x86_sep __devinitdata = 0;
> >  
>
> hm, I guess lots of things in there should be __cpuinit/__cpuinitdata. 

I'll try to do that.

> __devinit is a superset of that, but we're being a little wasteful in the
> case of CONFIG_HOTPLUG&&!CONFIG_HOTPLUG_CPU.

-- 
Chuck


             reply	other threads:[~2006-01-28  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28  6:04 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-26 18:36 Chuck Ebbert
2006-01-27 22:37 ` Andrew Morton

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=200601280106_MC3-1-B6F2-9A79@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.com \
    --cc=ergot86@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@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

all inboxes | Powered by JetHome®