public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: blauwirbel@gmail.com
Cc: anthony@codemonkey.ws, kvm@vger.kernel.org,
	sparclinux@vger.kernel.org, levon@movementarian.org,
	hollisb@us.ibm.com
Subject: Re: KVM for Sparc?
Date: Tue, 23 Sep 2008 13:38:56 -0700 (PDT)	[thread overview]
Message-ID: <20080923.133856.141663278.davem@davemloft.net> (raw)
In-Reply-To: <f43fc5580809230828i48be0e20m915814138b6a0e84@mail.gmail.com>

From: "Blue Swirl" <blauwirbel@gmail.com>
Date: Tue, 23 Sep 2008 18:28:06 +0300

> On 9/22/08, David Miller <davem@davemloft.net> wrote:
> > As he mentioned, the V8 rett instruction causes problems on V9 chips.
> >
> >  An opcode which was a V8 privileged instruction, "rett", got reused as
> >  a non-privileged instruction in V9, for "return".
> 
> There are others: rdtbr/flushw and stdfq/stqf. Also any ASI >0x80
> accesses are unprivileged on V9, though that shouldn't be a problem
> since all ASIs used on V8 were <0x80. And of course MMUs are
> incompatible.

Thanks for the list.  I sent a message to someone who I think might
have been responsible for these architectual design decisions, letting
them know what problems it is causing :-)

> >  So booting a 32-bit kernel on a 64-bit cpu is going to be challenging,
> >  at best.
> 
> Maybe it would be possible to run V8 userspace with full speed
> acceleration on V9 and use translation only for kernel code?

Yes, that should work.

BTW, there is another area related the ASIs.  Trap numbers.

Even through V9, traps only up to 0x7f are valid.  But sun4v extended
V9 to allow trap numbers >= 0x80, mostly these are used for hypervisor
calls.

The trap number field of the instruction is just extended one more
bit higher to accomodate this.

It turns out that binutils's assembler didn't range check the trap
number field value, so binutils needed no changes to support this :-)

  reply	other threads:[~2008-09-23 20:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f43fc5580809210538r38a29d8dpc74342a2bceea109@mail.gmail.com>
2008-09-21 12:52 ` KVM for Sparc? Blue Swirl
2008-09-22 19:34   ` Anthony Liguori
2008-09-22 20:18     ` Hollis Blanchard
2008-09-22 20:26       ` David Miller
2008-09-22 21:25         ` Hollis Blanchard
2008-09-22 22:14           ` David Miller
2008-09-23 15:34             ` Blue Swirl
2008-09-23 20:41               ` David Miller
2008-09-24 17:22                 ` Blue Swirl
2008-09-24 19:29                   ` David Miller
2008-09-22 20:31       ` Javier Guerra
2008-09-22 21:02         ` David Miller
2008-09-22 21:27         ` Hollis Blanchard
2008-09-22 22:15           ` David Miller
2008-09-23 15:52             ` Blue Swirl
2008-09-23 16:07             ` Hollis Blanchard
2008-09-23 20:44               ` David Miller
2008-09-22 20:24     ` David Miller
2008-09-23 15:28       ` Blue Swirl
2008-09-23 20:38         ` David Miller [this message]
2008-09-24 17:20           ` Blue Swirl
2008-09-24 18:06             ` Blue Swirl
2008-09-24 19:29               ` David Miller
2008-09-25 16:58                 ` Blue Swirl
2008-09-24 19:28             ` David Miller

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=20080923.133856.141663278.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=levon@movementarian.org \
    --cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox