From: Scott Wood <scottwood@freescale.com>
To: Liu Yu-B13201 <B13201@freescale.com>
Cc: 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 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt
Date: Wed, 04 Jan 2012 19:21:07 +0000 [thread overview]
Message-ID: <4F04A6A3.3050808@freescale.com> (raw)
In-Reply-To: <4CA99838F21AB847ACC344051E231709056D1BEE@039-SN2MPN1-022.039d.mgd.msft.net>
On 01/04/2012 03:23 AM, Liu Yu-B13201 wrote:
>
>
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Tuesday, January 03, 2012 2:23 AM
>> To: Liu Yu-B13201
>> Cc: agraf@suse.de; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for
>> paravirt guest linux
>>
>> Since this is standardized in ePAPR, can we move it out of kvm.c an into
>> generic code to work with any hypervisor that sets has-idle? Likewise
>> with kvm_para_setup().
>>
>
> Do you mean we scan and parse hypervisor node in early_init_devtree()?
No, just have a separate initcall for enabling ePAPR paravirt features.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Liu Yu-B13201 <B13201@freescale.com>
Cc: 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 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt guest linux
Date: Wed, 4 Jan 2012 13:21:07 -0600 [thread overview]
Message-ID: <4F04A6A3.3050808@freescale.com> (raw)
In-Reply-To: <4CA99838F21AB847ACC344051E231709056D1BEE@039-SN2MPN1-022.039d.mgd.msft.net>
On 01/04/2012 03:23 AM, Liu Yu-B13201 wrote:
>
>
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Tuesday, January 03, 2012 2:23 AM
>> To: Liu Yu-B13201
>> Cc: agraf@suse.de; kvm-ppc@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for
>> paravirt guest linux
>>
>> Since this is standardized in ePAPR, can we move it out of kvm.c an into
>> generic code to work with any hypervisor that sets has-idle? Likewise
>> with kvm_para_setup().
>>
>
> Do you mean we scan and parse hypervisor node in early_init_devtree()?
No, just have a separate initcall for enabling ePAPR paravirt features.
-Scott
next prev parent reply other threads:[~2012-01-04 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 6:16 [PATCH 1/2] KVM: PPC: epapr: Add idle hcall support for host Liu Yu
2011-12-31 6:16 ` Liu Yu
2011-12-31 6:16 ` [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt guest linux Liu Yu
2011-12-31 6:16 ` Liu Yu
2012-01-02 18:23 ` [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt Scott Wood
2012-01-02 18:23 ` [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt guest linux Scott Wood
2012-01-04 9:23 ` [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt Liu Yu-B13201
2012-01-04 9:23 ` [PATCH 2/2] KVM: PPC: epapr: Install ev_idle hcall for paravirt guest linux Liu Yu-B13201
2012-01-04 19:21 ` Scott Wood [this message]
2012-01-04 19:21 ` Scott Wood
2012-01-02 18:17 ` [PATCH 1/2] KVM: PPC: epapr: Add idle hcall support for host Scott Wood
2012-01-02 18:17 ` Scott Wood
2012-01-03 14:01 ` Avi Kivity
2012-01-03 14:01 ` Avi Kivity
2012-01-03 14:13 ` Alexander Graf
2012-01-03 14:13 ` Alexander Graf
2012-01-04 10:33 ` Avi Kivity
2012-01-04 10:33 ` Avi Kivity
2012-01-04 12:04 ` Alexander Graf
2012-01-04 12:04 ` Alexander Graf
2012-01-04 12:11 ` Avi Kivity
2012-01-04 12:11 ` Avi Kivity
2012-01-04 19:25 ` Scott Wood
2012-01-04 19:25 ` Scott Wood
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=4F04A6A3.3050808@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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.