From: Li Shaohua <shaohua.li@intel.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>,
ACPI-DEV <acpi-devel@lists.sourceforge.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>
Subject: Re: [RFC 1/6]SEP initialization rework
Date: Tue, 05 Apr 2005 09:00:25 +0800 [thread overview]
Message-ID: <1112662825.17861.4.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504041235001.30273@montezuma.fsmlabs.com>
On Tue, 2005-04-05 at 03:10, Zwane Mwaikambo wrote:
> On Mon, 4 Apr 2005, Li Shaohua wrote:
>
> > linux-2.6.11-root/arch/i386/kernel/smpboot.c | 6 ++++++
> > linux-2.6.11-root/arch/i386/kernel/sysenter.c | 10 ++++++----
> > linux-2.6.11-root/arch/i386/mach-voyager/voyager_smp.c | 6 ++++++
> > 3 files changed, 18 insertions(+), 4 deletions(-)
> >
> > diff -puN arch/i386/kernel/sysenter.c~sep_init_cleanup arch/i386/kernel/sysenter.c
> > --- linux-2.6.11/arch/i386/kernel/sysenter.c~sep_init_cleanup 2005-03-28 09:32:30.936304248 +0800
> > +++ linux-2.6.11-root/arch/i386/kernel/sysenter.c 2005-03-28 09:58:20.703703792 +0800
> > @@ -26,6 +26,11 @@ void enable_sep_cpu(void *info)
> > int cpu = get_cpu();
> > struct tss_struct *tss = &per_cpu(init_tss, cpu);
> >
> > + if (!boot_cpu_has(X86_FEATURE_SEP)) {
> > + put_cpu();
> > + return;
> > + }
> > +
>
> Do you have systems like this? Is it really skipping SEP if the boot
> processor doesn't have SEP?
No, I haven't such system. This is the logic of original SEP
initialization. If the CPU hasn't SEP, original logic doesn't call
'on_each_cpu(enable_sep_cpu,...)'.
Thanks,
Shaohua
next prev parent reply other threads:[~2005-04-05 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:05 Li Shaohua
2005-04-04 8:46 ` Pavel Machek
2005-04-04 8:52 ` Li Shaohua
2005-04-04 19:10 ` Zwane Mwaikambo
2005-04-05 1:00 ` Li Shaohua [this message]
2005-04-05 8:00 ` Zwane Mwaikambo
2005-04-06 19:31 ` Martin Waitz
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=1112662825.17861.4.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=zwane@arm.linux.org.uk \
/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®