From: Mike Kravetz <kravetz@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Workaround for RTAS bug
Date: Tue, 28 Mar 2006 11:42:30 -0800 [thread overview]
Message-ID: <20060328194230.GC5070@w-mikek2.ibm.com> (raw)
In-Reply-To: <20060327231959.GA15383@w-mikek2.ibm.com>
On Mon, Mar 27, 2006 at 03:20:00PM -0800, Mike Kravetz wrote:
> Also note that the 32 bit version of enter_rtas() should have the same
> work around even though the chances of hitting the bug are much smaller
> due to the lack of DLPAR on 32 bit kernels. However, my assembly skills
> are a bit rusty and the 32 bit code doesn't seem to follow the conventions
> for where things should be saved. In addition, I don't have a system
> to test 32 bit kernels. Help creating and at least touch testing the
> same workaround for 32 bit would be appreciated.
Upon further examination, there does not appear to be any exposure to
this issue on 32 bit kernels. Therefore, the original patch for 64 bit
should be the only workaround that is required.
--
Mike
prev parent reply other threads:[~2006-03-28 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 23:20 [PATCH] Workaround for RTAS bug Mike Kravetz
2006-03-28 19:42 ` Mike Kravetz [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=20060328194230.GC5070@w-mikek2.ibm.com \
--to=kravetz@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).