linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/15] celleb: interfaces to the hypervisor of Celleb
Date: Tue, 12 Dec 2006 15:42:39 +1100	[thread overview]
Message-ID: <1165898559.11914.18.camel@localhost.localdomain> (raw)
In-Reply-To: <200612121450.41561.jk@ozlabs.org>

> Also, do you need beat_errno? you return the same value in every 
> function anyway.

It's actually a very bad thing to have a global errno... It's racy, how
do you do if multiple CPUs modify it at the same time ? Thus the content
of it is worthless, so just drop it ;-)

Ben.
 

  reply	other threads:[~2006-12-12  4:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12  3:23 [PATCH 4/15] celleb: interfaces to the hypervisor of Celleb Ishizaki Kou
2006-12-12  3:50 ` Jeremy Kerr
2006-12-12  4:42   ` Benjamin Herrenschmidt [this message]
2006-12-12 17:31 ` Geoff Levand
2006-12-14  1:35   ` Ishizaki Kou
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 11:21 Ishizaki Kou
2006-12-12 20:13 ` Arnd Bergmann

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=1165898559.11914.18.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=jk@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.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).