From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Mihai Caraman <mihai.caraman@freescale.com>,
"<linuxppc-dev@lists.ozlabs.org>" <linuxppc-dev@lists.ozlabs.org>,
"<kvm@vger.kernel.org>" <kvm@vger.kernel.org>,
"<kvm-ppc@vger.kernel.org>" <kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] KVM: PPC: bookehv: Allow duplicate calls of DO_KVM macro
Date: Wed, 12 Sep 2012 16:38:05 -0500 [thread overview]
Message-ID: <505100BD.6020304@freescale.com> (raw)
In-Reply-To: <F4E2A678-6697-4207-8CEE-2CFB3629F554@suse.de>
On 09/12/2012 01:56 PM, Alexander Graf wrote:
>
>
> On 12.09.2012, at 15:18, Mihai Caraman <mihai.caraman@freescale.com> wrote:
>
>> The current form of DO_KVM macro restricts its use to one call per input
>> parameter set. This is caused by kvmppc_resume_\intno\()_\srr1 symbol
>> definition.
>> Duplicate calls of DO_KVM are required by distinct implementations of
>> exeption handlers which are delegated at runtime.
>
> Not sure I understand what you're trying to achieve here. Please elaborate ;)
On 64-bit book3e we compile multiple versions of the TLB miss handlers,
and choose from them at runtime. Without this patch, we get duplicate
label errors if more than one variant of the same exception uses DO_KVM.
-Scott
next prev parent reply other threads:[~2012-09-12 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 13:18 [PATCH] KVM: PPC: bookehv: Allow duplicate calls of DO_KVM macro Mihai Caraman
2012-09-12 18:56 ` Alexander Graf
2012-09-12 21:38 ` Scott Wood [this message]
2012-09-12 21:45 ` Alexander Graf
2012-09-12 21:54 ` Scott Wood
2012-09-13 12:50 ` Caraman Mihai Claudiu-B02008
2012-09-13 15:02 ` 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=505100BD.6020304@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mihai.caraman@freescale.com \
/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).