From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>, <kvm@vger.kernel.org>,
<kvm-ppc@vger.kernel.org>
Subject: Re: [PATCH] KVM: Add KVM_CAP_IRQ_ARCH capability
Date: Thu, 14 Mar 2013 14:10:58 -0500 [thread overview]
Message-ID: <1363288258.28440.11@snotra> (raw)
In-Reply-To: <76C38059-3AE6-45F3-9CAC-D3041FFEF54C@suse.de> (from agraf@suse.de on Thu Mar 14 14:03:30 2013)
On 03/14/2013 02:03:30 PM, Alexander Graf wrote:
>
> On 14.03.2013, at 19:35, Scott Wood wrote:
>
> > On 03/14/2013 01:33:30 PM, Alexander Graf wrote:
> >> On 14.03.2013, at 19:20, Scott Wood wrote:
> >> > On 03/13/2013 08:20:44 PM, Paul Mackerras wrote:
> >> >> Setting this capability on a vcpu connects that vcpu to an
> interrupt
> >> >> controller device. The args[0] field of the argument
> kvm_enable_cap
> >> >> struct specifies the overall architecture of the interrupt
> >> >> controller. The args[1] field specifies the CPU number for the
> vcpu
> >> >> from the interrupt controller's point of view.
> >> >> Signed-off-by: Paul Mackerras <paulus@samba.org>
> >> >> ---
> >> >> arch/powerpc/include/asm/kvm_host.h | 3 +++
> >> >> arch/powerpc/kvm/powerpc.c | 29
> +++++++++++++++++++++++++++++
> >> >> include/uapi/linux/kvm.h | 1 +
> >> >> 3 files changed, 33 insertions(+)
> >> >> diff --git a/arch/powerpc/include/asm/kvm_host.h
> b/arch/powerpc/include/asm/kvm_host.h
> >> >> index f4ba881..dd167e4 100644
> >> >> --- a/arch/powerpc/include/asm/kvm_host.h
> >> >> +++ b/arch/powerpc/include/asm/kvm_host.h
> >> >> @@ -373,6 +373,9 @@ struct kvmppc_booke_debug_reg {
> >> >> struct kvm_vcpu_arch {
> >> >> ulong host_stack;
> >> >> u32 host_pid;
> >> >> +
> >> >> + u32 intr_ctrler;
> >> >> +
> >> >
> >> > That abbreviation seems a bit awkward, and we should also have a
> >> > private-data pointer.
> >> >
> >> > How about:
> >> >
> >> > u32 irq_arch;
> >> We also want int pic_fd, no?
> >
> > Not sure we really need that on the vcpu. We'll need it on the vm
> unless we add it as an arg to the vcpu cap enable.
>
> I don't think we need anything vm global for the cpu <-> PIC
> connections.
The two components have to link up somehow. If the vcpu cap enable
ioctl doesn't specify it, then the device creation will have to stick a
reference to itself somewhere in the vm.
> Also, if you want to deregister a CPU (hotplug remove), you probably
> want to tell the PIC that the CPU has gone.
Yes, I mentioned that in my previous e-mail.
-Scott
next prev parent reply other threads:[~2013-03-14 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 1:20 [PATCH] KVM: Add KVM_CAP_IRQ_ARCH capability Paul Mackerras
2013-03-14 18:20 ` Scott Wood
2013-03-14 18:33 ` Alexander Graf
2013-03-14 18:35 ` Scott Wood
2013-03-14 19:03 ` Alexander Graf
2013-03-14 19:10 ` Scott Wood [this message]
2013-03-14 21:46 ` Alexander Graf
2013-03-14 22:28 ` Paul Mackerras
2013-03-14 22:38 ` Scott Wood
2013-03-14 22:19 ` Paul Mackerras
2013-03-14 22:41 ` 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=1363288258.28440.11@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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