public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: "Cédric Le Goater" <clg@fr.ibm.com>,
	kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
	"Alexey Kardashevskiy" <aik@ozlabs.ru>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: return htab entries in big endian
Date: Fri, 3 Oct 2014 22:05:07 +1000	[thread overview]
Message-ID: <20141003120507.GA10764@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <542D8620.2060503@suse.de>

On Thu, Oct 02, 2014 at 07:06:40PM +0200, Alexander Graf wrote:
> 
> I think we're best off to keep the user space API native endian. So
> really we should only ever have to convert from big to native endian on
> read and native to big on write.
> 
> With that QEMU should do the "right thing" already, no?

I believe that when migrating a guest, QEMU just passes the byte
stream it gets from the htab fd along to the destination QEMU with
little or no interpretation, and the destination QEMU writes the byte
stream to the htab fd for the receiving VM. Alexey would be able to
say for sure.

If that's the case, then perhaps it's best to define that byte stream
to contain values of one specific endianness, and for compatibility
that would be big endian.

I assume we would want to be able to migrate a guest from a BE host to
an LE host or vice versa. If not then the question is moot.

Paul.

  reply	other threads:[~2014-10-03 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 16:58 [PATCH] KVM: PPC: Book3S HV: return htab entries in big endian Cédric Le Goater
2014-10-02 17:06 ` Alexander Graf
2014-10-03 12:05   ` Paul Mackerras [this message]
2014-10-03 21:05     ` Alexander Graf
2014-10-04  3:42       ` Alexey Kardashevskiy

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=20141003120507.GA10764@iris.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=clg@fr.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@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