From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stuart Yoder <stuart.yoder@freescale.com>,
kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v9 4/4] KVM: PPC: epapr: Update other hypercall invoking
Date: Wed, 07 Mar 2012 23:40:53 +0000 [thread overview]
Message-ID: <4F57F205.2070104@freescale.com> (raw)
In-Reply-To: <376AD217-0420-4558-BA47-B5AF39C21A21@suse.de>
On 03/07/2012 05:37 PM, Alexander Graf wrote:
>
> On 08.03.2012, at 00:12, Stuart Yoder wrote:
>
>> diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig
>> index f1ea59b..9ac4bc6 100644
>> --- a/drivers/tty/Kconfig
>> +++ b/drivers/tty/Kconfig
>> @@ -354,6 +354,7 @@ config TRACE_SINK
>> config PPC_EPAPR_HV_BYTECHAN
>> tristate "ePAPR hypervisor byte channel driver"
>> depends on PPC
>> + select EPAPR_PARAVIRT
>> help
>> This driver creates /dev entries for each ePAPR hypervisor byte
>> channel, thereby allowing applications to communicate with byte
>> diff --git a/drivers/virt/Kconfig b/drivers/virt/Kconfig
>> index 2dcdbc9..99ebdde 100644
>> --- a/drivers/virt/Kconfig
>> +++ b/drivers/virt/Kconfig
>> @@ -15,6 +15,7 @@ if VIRT_DRIVERS
>> config FSL_HV_MANAGER
>> tristate "Freescale hypervisor management driver"
>> depends on FSL_SOC
>> + select EPAPR_PARAVIRT
>
> Do you maybe have older versions of topaz that don't expose a /hypervisor node for which you want to have fallback code in?
Probably not that lack a /hypervisor altogether, but it's possible
someone's using a Topaz that's too old to have hcall-instructions, which
was added about a year and a half ago.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Stuart Yoder <stuart.yoder@freescale.com>,
<kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH v9 4/4] KVM: PPC: epapr: Update other hypercall invoking
Date: Wed, 7 Mar 2012 17:40:53 -0600 [thread overview]
Message-ID: <4F57F205.2070104@freescale.com> (raw)
In-Reply-To: <376AD217-0420-4558-BA47-B5AF39C21A21@suse.de>
On 03/07/2012 05:37 PM, Alexander Graf wrote:
>
> On 08.03.2012, at 00:12, Stuart Yoder wrote:
>
>> diff --git a/drivers/tty/Kconfig b/drivers/tty/Kconfig
>> index f1ea59b..9ac4bc6 100644
>> --- a/drivers/tty/Kconfig
>> +++ b/drivers/tty/Kconfig
>> @@ -354,6 +354,7 @@ config TRACE_SINK
>> config PPC_EPAPR_HV_BYTECHAN
>> tristate "ePAPR hypervisor byte channel driver"
>> depends on PPC
>> + select EPAPR_PARAVIRT
>> help
>> This driver creates /dev entries for each ePAPR hypervisor byte
>> channel, thereby allowing applications to communicate with byte
>> diff --git a/drivers/virt/Kconfig b/drivers/virt/Kconfig
>> index 2dcdbc9..99ebdde 100644
>> --- a/drivers/virt/Kconfig
>> +++ b/drivers/virt/Kconfig
>> @@ -15,6 +15,7 @@ if VIRT_DRIVERS
>> config FSL_HV_MANAGER
>> tristate "Freescale hypervisor management driver"
>> depends on FSL_SOC
>> + select EPAPR_PARAVIRT
>
> Do you maybe have older versions of topaz that don't expose a /hypervisor node for which you want to have fallback code in?
Probably not that lack a /hypervisor altogether, but it's possible
someone's using a Topaz that's too old to have hcall-instructions, which
was added about a year and a half ago.
-Scott
next prev parent reply other threads:[~2012-03-07 23:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 23:12 [PATCH v9 0/4] KVM: PPC: Add ePAPR idle hcall support Stuart Yoder
2012-03-07 23:12 ` Stuart Yoder
2012-03-07 23:12 ` [PATCH v9 1/4] KVM: PPC: epapr: Factor out the epapr init Stuart Yoder
2012-03-07 23:12 ` Stuart Yoder
2012-03-07 23:19 ` Alexander Graf
2012-03-07 23:19 ` Alexander Graf
2012-03-15 19:50 ` Stuart Yoder
2012-03-15 19:50 ` Stuart Yoder
2012-03-07 23:12 ` [PATCH v9 2/4] KVM: PPC: epapr: Add idle hcall support for host Stuart Yoder
2012-03-07 23:12 ` Stuart Yoder
2012-03-07 23:27 ` Alexander Graf
2012-03-07 23:27 ` Alexander Graf
2012-03-07 23:37 ` Scott Wood
2012-03-07 23:37 ` Scott Wood
2012-03-07 23:38 ` Alexander Graf
2012-03-07 23:38 ` Alexander Graf
2012-03-08 4:18 ` Yoder Stuart-B08248
2012-03-08 4:18 ` Yoder Stuart-B08248
2012-03-08 12:20 ` Alexander Graf
2012-03-08 12:20 ` Alexander Graf
2012-03-15 15:56 ` Stuart Yoder
2012-03-15 15:56 ` Stuart Yoder
2012-03-07 23:12 ` [PATCH v9 3/4] KVM: PPC: epapr: install ev_idle hcall for e500 guest Stuart Yoder
2012-03-07 23:12 ` Stuart Yoder
2012-03-07 23:36 ` Alexander Graf
2012-03-07 23:36 ` Alexander Graf
2012-03-07 23:12 ` [PATCH v9 4/4] KVM: PPC: epapr: Update other hypercall invoking Stuart Yoder
2012-03-07 23:12 ` Stuart Yoder
2012-03-07 23:37 ` Alexander Graf
2012-03-07 23:37 ` Alexander Graf
2012-03-07 23:40 ` Scott Wood [this message]
2012-03-07 23:40 ` 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=4F57F205.2070104@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=stuart.yoder@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 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.