From: Scott Wood <scottwood@freescale.com>
To: Liu Yu-B13201 <B13201@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Wood Scott-B07421 <B07421@freescale.com>,
"agraf@suse.de" <agraf@suse.de>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] KVM: PPC: epapr: Factor out the epapr init
Date: Mon, 13 Feb 2012 11:15:23 -0600 [thread overview]
Message-ID: <4F39452B.2030202@freescale.com> (raw)
In-Reply-To: <4CA99838F21AB847ACC344051E231709057158DE@039-SN2MPN1-022.039d.mgd.msft.net>
On 02/12/2012 11:47 PM, Liu Yu-B13201 wrote:
>
>
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Saturday, February 11, 2012 2:40 AM
>> To: Liu Yu-B13201
>> Cc: agraf@suse.de; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org;
>> linuxppc-dev@ozlabs.org; Wood Scott-B07421
>> Subject: Re: [PATCH v3 1/3] KVM: PPC: epapr: Factor out the epapr init
>>
>> Why are you still doing the patching inside kvm.c?
>>
>
> Do you mean we should move kvm_hypercall_start() into epapr bit?
Yes. This is an ePAPR mechanism; KVM just happens to be a user of it.
We should also update arch/powerpc/include/asm/epapr_hcalls.h to use
this mechanism.
-Scott
prev parent reply other threads:[~2012-02-13 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 10:02 [PATCH v3 1/3] KVM: PPC: epapr: Factor out the epapr init Liu Yu
2012-02-10 10:02 ` [PATCH v3 2/3] KVM: PPC: epapr: Add idle hcall support for host Liu Yu
2012-02-10 10:02 ` [PATCH v3 3/3] KVM: PPC: epapr: install ev_idle hcall for e500 guest Liu Yu
2012-02-10 18:41 ` Scott Wood
2012-02-10 18:39 ` [PATCH v3 1/3] KVM: PPC: epapr: Factor out the epapr init Scott Wood
2012-02-13 5:47 ` Liu Yu-B13201
2012-02-13 17:15 ` Scott Wood [this message]
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=4F39452B.2030202@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B13201@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--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).