At present, PR KVM and BookE KVM does multiple copies of FP and
related state because of the way that they use the arrays in the
thread_struct as an intermediate staging post for the state. They do
this so that they can use the existing system functions for loading
and saving state, and so
On 09.09.2013, at 09:28, Michael Neuling wrote:
At present, PR KVM and BookE KVM does multiple copies of FP and
related state because of the way that they use the arrays in the
thread_struct as an intermediate staging post for the state. They do
this so that they can use the existing system
On Fri, Sep 06, 2013 at 07:20:19PM +0100, Yoder Stuart-B08248 wrote:
Adding Will...
[...]
I have a query about the ARM SMMU driver. In the ARM smmu driver I see,
that bus notifiers are registered for both amba and platform bus. Amba is
the I/O interconnect, right? Why is bus notifier
Hi Will,
Just trying to understand the scope of platform device assignment to guest on
ARM. So, are the AMBA devices also represented in the device tree?
Regards
Varun
-Original Message-
From: kvm-ppc-ow...@vger.kernel.org [mailto:kvm-ppc-
ow...@vger.kernel.org] On Behalf Of Will
Alexander Graf ag...@suse.de wrote:
On 09.09.2013, at 09:28, Michael Neuling wrote:
At present, PR KVM and BookE KVM does multiple copies of FP and
related state because of the way that they use the arrays in the
thread_struct as an intermediate staging post for the state. They do
On 09.09.2013, at 11:38, Michael Neuling wrote:
Alexander Graf ag...@suse.de wrote:
On 09.09.2013, at 09:28, Michael Neuling wrote:
At present, PR KVM and BookE KVM does multiple copies of FP and
related state because of the way that they use the arrays in the
thread_struct as an
