From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
kvm-ppc@vger.kernel.org,
"<kvmarm@lists.cs.columbia.edu>" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [RFC PATCH 0/9] KVM: PPC: In-kernel PAPR interrupt controller emulation
Date: Thu, 10 Jan 2013 19:06:01 +0000 [thread overview]
Message-ID: <1357844761.27576.3@snotra> (raw)
In-Reply-To: <79ED47F9-8C2E-4171-A930-C95B5E29387C@suse.de> (from agraf@suse.de on Thu Jan 10 05:42:16 2013)
On 01/10/2013 05:42:16 AM, Alexander Graf wrote:
> Other instantiation attributes we don't know that early on should be
> settable between the time frame of vm creation and first execution.
> An example for this are device addresses. Check out the threads "KVM:
> ARM: Rename KVM_SET_DEVICE_ADDRESS" and "KVM: ARM: Introduce
> KVM_SET_DEVICE_ADDRESS ioctl" for more information on this particular
> bit.
FWIW, on Freescale chips the MPIC base address can move at runtime if
the guest writes to CCSRBAR (though QEMU doesn't currently implement
this).
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"kvm@vger.kernel.org list" <kvm@vger.kernel.org>,
<kvm-ppc@vger.kernel.org>,
"<kvmarm@lists.cs.columbia.edu>" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [RFC PATCH 0/9] KVM: PPC: In-kernel PAPR interrupt controller emulation
Date: Thu, 10 Jan 2013 13:06:01 -0600 [thread overview]
Message-ID: <1357844761.27576.3@snotra> (raw)
In-Reply-To: <79ED47F9-8C2E-4171-A930-C95B5E29387C@suse.de> (from agraf@suse.de on Thu Jan 10 05:42:16 2013)
On 01/10/2013 05:42:16 AM, Alexander Graf wrote:
> Other instantiation attributes we don't know that early on should be
> settable between the time frame of vm creation and first execution.
> An example for this are device addresses. Check out the threads "KVM:
> ARM: Rename KVM_SET_DEVICE_ADDRESS" and "KVM: ARM: Introduce
> KVM_SET_DEVICE_ADDRESS ioctl" for more information on this particular
> bit.
FWIW, on Freescale chips the MPIC base address can move at runtime if
the guest writes to CCSRBAR (though QEMU doesn't currently implement
this).
-Scott
next prev parent reply other threads:[~2013-01-10 19:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 3:18 [RFC PATCH 0/9] KVM: PPC: In-kernel PAPR interrupt controller emulation Paul Mackerras
2012-11-05 3:18 ` Paul Mackerras
2012-11-05 3:19 ` [RFC PATCH 1/9] KVM: PPC: Remove unused argument to kvmppc_core_dequeue_external Paul Mackerras
2012-11-05 3:19 ` Paul Mackerras
2012-11-05 3:20 ` [RFC PATCH 2/9] KVM: PPC: Book3S: Add infrastructure to implement kernel-side RTAS calls Paul Mackerras
2012-11-05 3:20 ` Paul Mackerras
2012-11-05 3:21 ` [RFC PATCH 3/9] KVM: PPC: Book3S: Add kernel emulation for the XICS interrupt controller Paul Mackerras
2012-11-05 3:21 ` Paul Mackerras
2012-11-05 3:21 ` [RFC PATCH 4/9] KVM: PPC: Book3S HV: Speed up wakeups of CPUs on HV KVM Paul Mackerras
2012-11-05 3:21 ` Paul Mackerras
2012-11-05 3:22 ` [RFC PATCH 5/9] KVM: PPC: Book3S HV: Add support for real mode ICP in XICS emulation Paul Mackerras
2012-11-05 3:22 ` Paul Mackerras
2012-11-05 3:23 ` [RFC PATCH 6/9] KVM: PPC: Book3S HV: Improve real-mode handling of external interrupts Paul Mackerras
2012-11-05 3:23 ` Paul Mackerras
2012-11-05 3:23 ` [RFC PATCH 7/9] KVM: PPC: Book3S: Add support for ibm,int-on/off RTAS calls Paul Mackerras
2012-11-05 3:23 ` Paul Mackerras
2012-11-05 3:24 ` [RFC PATCH 8/9] KVM: PPC: Book3S: Facilities to save/restore XICS presentation ctrler state Paul Mackerras
2012-11-05 3:24 ` Paul Mackerras
2012-11-05 3:25 ` [RFC PATCH 9/9] KVM: PPC: Book 3S: Facilities to save/restore XICS source controller state Paul Mackerras
2012-11-05 3:25 ` Paul Mackerras
2012-12-15 0:46 ` [RFC PATCH 0/9] KVM: PPC: In-kernel PAPR interrupt controller emulation Alexander Graf
2012-12-15 0:46 ` Alexander Graf
2012-12-15 2:06 ` Benjamin Herrenschmidt
2012-12-15 2:06 ` Benjamin Herrenschmidt
2013-01-10 5:09 ` Paul Mackerras
2013-01-10 5:09 ` Paul Mackerras
2013-01-10 11:42 ` Alexander Graf
2013-01-10 11:42 ` Alexander Graf
2013-01-10 19:06 ` Scott Wood [this message]
2013-01-10 19:06 ` Scott Wood
2013-01-21 0:08 ` Paul Mackerras
2013-01-21 0:08 ` Paul Mackerras
2013-01-21 0:22 ` Alexander Graf
2013-01-21 0:22 ` Alexander Graf
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=1357844761.27576.3@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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 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.