linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: kvm-ppc-devel@lists.sourceforge.net
Cc: kvm-devel@lists.sourceforge.net, linuxppc-dev@ozlabs.org,
	Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [kvm-ppc-devel] [PATCH 3 of 3] [KVM POWERPC] PowerPC 440 KVM implementation
Date: Tue, 8 Apr 2008 07:09:31 +0200	[thread overview]
Message-ID: <200804080709.32022.arnd@arndb.de> (raw)
In-Reply-To: <200804072319.11677.hollisb@us.ibm.com>

On Tuesday 08 April 2008, Hollis Blanchard wrote:
> If there is one thing I have learned in my various porting efforts, it's that 
> using a variable-sized type in an interface is just begging for trouble.
> 
> x86 uses fixed 64-bit variables here (even with x86-32), so that might be the 
> right solution here.

Right, I think there was even a conference presentation about this topic
done by one of us, right?

	Arnd <><

  reply	other threads:[~2008-04-08  5:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 20:53 [PATCH 0 of 3] KVM for PowerPC 440 Hollis Blanchard
2008-04-07 20:53 ` [PATCH 1 of 3] [POWERPC 44x] Export tlb_44x_hwater for KVM Hollis Blanchard
2008-04-10 14:30   ` Josh Boyer
2008-04-07 20:53 ` [PATCH 2 of 3] [KVM] Add DCR access information to struct kvm_run Hollis Blanchard
2008-04-08  1:11   ` David Gibson
2008-04-08  3:25     ` Hollis Blanchard
2008-04-08  3:54       ` David Gibson
2008-04-08  4:06         ` Hollis Blanchard
2008-04-08  4:16           ` David Gibson
2008-04-10 16:47         ` Josh Boyer
2008-04-07 20:53 ` [PATCH 3 of 3] [KVM POWERPC] PowerPC 440 KVM implementation Hollis Blanchard
2008-04-08  2:12   ` Josh Boyer
2008-04-08  4:00     ` Hollis Blanchard
2008-04-08  2:58   ` Arnd Bergmann
2008-04-08  4:19     ` Hollis Blanchard
2008-04-08  5:09       ` Arnd Bergmann [this message]
2008-04-10 11:55 ` [PATCH 0 of 3] KVM for PowerPC 440 Josh Boyer
2008-04-10 14:26   ` Hollis Blanchard

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=200804080709.32022.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).