From: Alexander Graf <agraf@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 6/7] KVM: PPC: Book3S HV: Fix ABIv2 on LE
Date: Wed, 18 Jun 2014 15:23:36 +0000 [thread overview]
Message-ID: <53A1AEF8.9000904@suse.de> (raw)
In-Reply-To: <87ha3ickfp.fsf@linux.vnet.ibm.com>
On 18.06.14 17:21, Aneesh Kumar K.V wrote:
> Alexander Graf <agraf@suse.de> writes:
>
>> We use ABIv2 on Little Endian systems which gets rid of the dotted function
>> names. Branch to the actual functions when we see such a system.
>>
>> Signed-off-by: Alexander Graf <agraf@suse.de>
> As per patches sent by anton we don't need this. We can branch to the
> function rathen than the dot symbol
>
> http://article.gmane.org/gmane.linux.ports.ppc.embedded/68925
> http://article.gmane.org/gmane.linux.ports.ppc.embedded/71005
Ah, true in this case, because the file never gets compiled as a module.
Alex
next prev parent reply other threads:[~2014-06-18 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 16:17 [PATCH 0/7] KVM: PPC: Book3S HV: Enable on little endian hosts Alexander Graf
2014-06-17 16:17 ` [PATCH 1/7] PPC: Add asm helpers for BE 32bit load/store Alexander Graf
2014-06-17 16:17 ` [PATCH 2/7] KVM: PPC: Book3S HV: Make HTAB code LE host aware Alexander Graf
2014-06-17 16:17 ` [PATCH 3/7] KVM: PPC: Book3S HV: Access guest VPA in BE Alexander Graf
2014-06-17 16:17 ` [PATCH 4/7] KVM: PPC: Book3S HV: Access host lppaca and shadow slb " Alexander Graf
2014-06-17 16:17 ` [PATCH 5/7] KVM: PPC: Book3S HV: Access XICS " Alexander Graf
2014-06-17 16:17 ` [PATCH 6/7] KVM: PPC: Book3S HV: Fix ABIv2 on LE Alexander Graf
2014-06-18 15:33 ` Aneesh Kumar K.V
2014-06-18 15:23 ` Alexander Graf [this message]
2014-06-24 13:34 ` [PATCH v3 " Alexander Graf
2014-06-17 16:17 ` [PATCH 7/7] KVM: PPC: Book3S HV: Enable for little endian hosts Alexander Graf
2014-07-04 7:41 ` [PATCH 0/7] KVM: PPC: Book3S HV: Enable on " Alexander Graf
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=53A1AEF8.9000904@suse.de \
--to=agraf@suse.de \
--cc=aneesh.kumar@linux.vnet.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