linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Suresh E. Warrier" <warrier@linux.vnet.ibm.com>,
	kvm@vger.kernel.org, linuxppc-dev@ozlabs.org
Cc: warrier@linux.vnet.ibm.com, paulus@samba.org, agraf@suse.de
Subject: Re: [v2,3/9] powerpc/powernv: Add icp_native_cause_ipi_rm
Date: Mon,  7 Dec 2015 17:38:18 +1100 (AEDT)	[thread overview]
Message-ID: <20151207063818.69F79140319@ozlabs.org> (raw)
In-Reply-To: <1448495096-24759-4-git-send-email-warrier@linux.vnet.ibm.com>

Subject would be better as "powerpc/xics".

On Wed, 2015-25-11 at 23:44:50 UTC, "Suresh E. Warrier" wrote:
> Function to cause an IPI. Requires kvm_hstate.xics_phys
> to be initialized with physical address of XICS.

Please expand the change log a bit, this is a bit terse.

> diff --git a/arch/powerpc/sysdev/xics/icp-native.c b/arch/powerpc/sysdev/xics/icp-native.c
> index eae3265..e39b18a 100644
> --- a/arch/powerpc/sysdev/xics/icp-native.c
> +++ b/arch/powerpc/sysdev/xics/icp-native.c
> @@ -159,6 +159,25 @@ static void icp_native_cause_ipi(int cpu, unsigned long data)
>  	icp_native_set_qirr(cpu, IPI_PRIORITY);
>  }
>  
> +void icp_native_cause_ipi_rm(int cpu)
> +{
> +	/*
> +	 * Currently not used to send IPIs to another CPU
> +	 * on the same core. Only caller is KVM real mode.
> +	 * Need the physical address of the XICS to be
> +	 * previously saved in kvm_hstate in the paca.
> +	 */
> +	unsigned long xics_phys;
> +
> +	/*
> +	 * Just like the cause_ipi functions, it is required to
> +	 * include a full barrier (out8 includes a sync) before
> +	 * causing the IPI.
> +	 */
> +	xics_phys = paca[cpu].kvm_hstate.xics_phys;
> +	out_rm8((u8 *)(xics_phys + XICS_MFRR), IPI_PRIORITY);
> +}

This doesn't build without KVM:

  arch/powerpc/sysdev/xics/icp-native.c:177:23: error: 'struct paca_struct' has no member named 'kvm_hstate'


Probably the whole function should be #ifdef CONFIG_KVM_BOOK3S_64_HV or
something.

cheers

  reply	other threads:[~2015-12-07  6:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 23:44 [PATCH v2 0/9] KVM: PPC: Book3S HV: Optimize wakeup VCPU from H_IPI Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 1/9] powerpc/smp: Support more IPI messages Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 2/9] powerpc/smp: Add smp_muxed_ipi_set_message Suresh Warrier
2015-12-07  6:35   ` [v2,2/9] " Michael Ellerman
2015-11-25 23:44 ` [PATCH v2 3/9] powerpc/powernv: Add icp_native_cause_ipi_rm Suresh Warrier
2015-12-07  6:38   ` Michael Ellerman [this message]
2015-11-25 23:44 ` [PATCH v2 4/9] KVM: PPC: Book3S HV: Host-side RM data structures Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 5/9] KVM: PPC: Book3S HV: Manage core host state Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 6/9] KVM: PPC: Book3S HV: kvmppc_host_rm_ops - handle offlining CPUs Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 7/9] KVM: PPC: Book3S HV: Host side kick VCPU when poked by real-mode KVM Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 8/9] KVM: PPC: Book3S HV: Send IPI to host core to wake VCPU Suresh Warrier
2015-11-25 23:44 ` [PATCH v2 9/9] KVM: PPC: Book3S HV: Add tunable to control H_IPI redirection Suresh Warrier

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=20151207063818.69F79140319@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=warrier@linux.vnet.ibm.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).