From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jimi Xenidis <jimix@watson.ibm.com>
Cc: Olof Johansson <olof@lixom.net>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Don't access HID registers if running on a Hypervisor.
Date: Thu, 22 Jun 2006 22:09:43 +1000 [thread overview]
Message-ID: <1150978183.3633.49.camel@localhost.localdomain> (raw)
In-Reply-To: <6BBF4F7C-1375-41FF-8D42-43BEC67194CC@watson.ibm.com>
On Thu, 2006-06-22 at 06:58 -0400, Jimi Xenidis wrote:
> 970s consider this a no-op (I believe an expensive one) especially
> when you consider some of the synchronization issues around the mtspr
> HIDx.
> And though this is 970 specific code, Cell and future processors,
> will no longer allow writing to to these registers if !(MSR[0]=1 &&
> MSR[PR]=0)
Fair enough, let's fix it.
Ben.
next prev parent reply other threads:[~2006-06-22 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 23:15 [PATCH] Don't access HID registers if running on a Hypervisor Jimi Xenidis
2006-06-21 23:51 ` Olof Johansson
2006-06-22 10:58 ` Jimi Xenidis
2006-06-22 12:09 ` Benjamin Herrenschmidt [this message]
2006-06-21 23:58 ` Paul Mackerras
2006-06-22 2:35 ` Jimi Xenidis
2006-06-22 16:23 ` Olof Johansson
2006-06-22 17:22 ` Jimi Xenidis
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=1150978183.3633.49.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jimix@watson.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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