From: Paul Mackerras <paulus@samba.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, Alexey Kardashevskiy <aik@ozlabs.ru>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 1/2] vfio powerpc: enabled on powernv platform
Date: Mon, 25 Feb 2013 13:21:46 +1100 [thread overview]
Message-ID: <20130225022146.GC12404@drongo> (raw)
In-Reply-To: <1360621003.12392.117.camel@bling.home>
On Mon, Feb 11, 2013 at 03:16:43PM -0700, Alex Williamson wrote:
>
> Why do these all return long (vs int)? Is this a POWER-ism?
On ppc64 the compiler tends to generate slightly shorter code with
longs than with ints. The reason is that with ints the compiler has
to put in "extend sign word" instructions to convert 64-bit values
from arithmetic instructions to values in the 32-bit range.
Paul.
next prev parent reply other threads:[~2013-02-25 2:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 11:54 [PATCH 0/2] vfio on power Alexey Kardashevskiy
2013-02-11 11:54 ` [PATCH 1/2] vfio powerpc: enabled on powernv platform Alexey Kardashevskiy
2013-02-11 22:16 ` Alex Williamson
2013-02-11 23:19 ` Alexey Kardashevskiy
2013-02-12 0:01 ` Alex Williamson
2013-02-25 2:21 ` Paul Mackerras [this message]
2013-02-11 11:54 ` [PATCH 2/2] vfio powerpc: implemented IOMMU driver for VFIO Alexey Kardashevskiy
2013-02-11 22:17 ` Alex Williamson
2013-02-11 23:45 ` Alexey Kardashevskiy
2013-02-12 0:25 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 9:03 [PATCH 0/2] vfio powerpc: implemented and enabled Alexey Kardashevskiy
2012-12-03 2:52 ` [PATCH 0/2] vfio on power: yet another try Alexey Kardashevskiy
2012-12-03 2:52 ` [PATCH 1/2] vfio powerpc: enabled on powernv platform Alexey Kardashevskiy
2012-12-03 17:35 ` Alex Williamson
2012-12-04 8:12 ` Alexey Kardashevskiy
2012-12-04 15:51 ` Alex Williamson
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=20130225022146.GC12404@drongo \
--to=paulus@samba.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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).