From: ebiederm@xmission.com (Eric W. Biederman)
To: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: safe_smp_processor_id i386 and x86_64
Date: Wed, 11 Oct 2006 10:58:21 -0600 [thread overview]
Message-ID: <m1y7rmlrgy.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <eg60ej$qqe$1@sea.gmane.org> (Aneesh Kumar K. V.'s message of "Fri, 06 Oct 2006 22:02:17 +0530")
"Aneesh Kumar K.V" <aneesh.kumar@gmail.com> writes:
> I was looking at the git log and the below changes confused me.
They are being used to solve different problems.
smp_processor_id on i386 doesn't work when a stack overflow
occurs. safe_smp_processor_id does.
On x86_64 since it is a simple register value we don't have that problem.
Eric
prev parent reply other threads:[~2006-10-11 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 16:32 Aneesh Kumar K.V
2006-10-11 16:58 ` Eric W. Biederman [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=m1y7rmlrgy.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=aneesh.kumar@gmail.com \
--cc=linux-kernel@vger.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®