From: Valdis.Kletnieks@vt.edu
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Gleb Natapov <gleb@kernel.org>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Subject: Re: Silence compiler warning in arch/x86/kvm/emulate.c
Date: Fri, 19 Feb 2016 19:33:44 -0500 [thread overview]
Message-ID: <19233.1455928424@turing-police.cc.vt.edu> (raw)
In-Reply-To: <56C75735.3010602@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Fri, 19 Feb 2016 18:56:05 +0100, Paolo Bonzini said:
> On 19/02/2016 18:54, Valdis.Kletnieks@vt.edu wrote:
> > But under what conditions is 'la' a 64-bit quantity that has any
> > bits set in the high 32 bits (meaning it's a pointer to something
> > over the 4G line) - but it's still valid to smash those bits?
>
> That can happen for example if there is a non-zero segment base. Then
> the linear address wraps at 4G.
Gaah.
Obviously, the concept that software could actually depend on a segment base
pointing at the 3G line (or whatever) to wrap around and be used to address
memory down in the first gig of RAM was too bizarre for my brain to visualize.
:)
The IBM S/360 with 24 bit addresses and S/370 with 24 or 31 bit addresses would
allow some instructions (most famously MVCL Move Character Long) to start
operating at the high end of memory and wrap around to the beginning. The
system documentation was pretty clear that although this *worked*, it was
probably not what you actually wanted to do.... :)
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
prev parent reply other threads:[~2016-02-20 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 21:49 Valdis Kletnieks
2016-02-19 11:11 ` Aurelien Jarno
2016-02-19 12:05 ` Paolo Bonzini
2016-02-19 17:04 ` Aurelien Jarno
2016-02-19 16:45 ` Aurelien Jarno
2016-02-19 17:54 ` Valdis.Kletnieks
2016-02-19 17:56 ` Paolo Bonzini
2016-02-20 0:33 ` Valdis.Kletnieks [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=19233.1455928424@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=aruna.hewapathirane@gmail.com \
--cc=aurelien@aurel32.net \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=x86@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®