From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ld2.acq - sign extension?
Date: Mon, 19 May 2008 12:25:51 +0000 [thread overview]
Message-ID: <483171CF.5060701@sgi.com> (raw)
In-Reply-To: <yq0wslqiqyp.fsf@jaguar.mkp.net>
Matthew Chapman wrote:
> Jes,
>
> You mentioned that you're running on KVM... while I don't know much
> about how KVM works, is that load instruction being intercepted and
> emulated by any chance? (Considering that it looks like something that
> would be accessing hardware registers on a real machine.) A bug in that
> emulation could explain why it's behaving strangely...
Hi Matt,
That has to be the reason - I was sitting here being convinced it
wasn't emulated because it's not a priviledged instruction, but
obviously it is given it's accessing the emulated registers.
Next I need to figure out how thats handled, whether it's a KVM bug
a hypervisor bug ..... all this fun we are having.
Cheers,
Jes
next prev parent reply other threads:[~2008-05-19 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 9:27 ld2.acq - sign extension? Jes Sorensen
2008-05-19 9:46 ` Andreas Schwab
2008-05-19 9:55 ` Jes Sorensen
2008-05-19 10:31 ` Avi Kivity
2008-05-19 12:12 ` Matthew Chapman
2008-05-19 12:25 ` Jes Sorensen [this message]
2008-05-19 12:51 ` Jes Sorensen
2008-05-20 4:48 ` Xu, Anthony
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=483171CF.5060701@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.