Hi Sasha,
On Thu, Aug 2, 2012 at 5:29 PM, Sasha Levin levinsasha...@gmail.com wrote:
Use the new KVM_SIGNAL_MSI ioctl to inject interrupts directly.
We still create GSIs and keep them for two reasons:
- They're required by virtio-* devices.
- There's not much overhead since we just create
On 08/04/2012 11:14 AM, Pekka Enberg wrote:
Hi Sasha,
On Thu, Aug 2, 2012 at 5:29 PM, Sasha Levin levinsasha...@gmail.com wrote:
Use the new KVM_SIGNAL_MSI ioctl to inject interrupts directly.
We still create GSIs and keep them for two reasons:
- They're required by virtio-* devices.
-
On 08/04/2012 11:14 AM, Pekka Enberg wrote:
This patch makes 'make check' hang for me. Full boot log below:
On Sat, Aug 4, 2012 at 12:30 PM, Sasha Levin levinsasha...@gmail.com wrote:
Is your host kernel running 3.5? The new MSI injection ioctl is a new 3.5
feature.
No, it's not running 3.5.
Am 03.08.2012 14:51, schrieb Peter Maydell:
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a list of KVM supporting architectures.
Add a default case for the common Linux architecture name and
QEMU
Thanks, applied.
On Tue, Jul 17, 2012 at 4:31 AM, Chegu Vinod chegu_vi...@hp.com wrote:
Changes since v3:
- using bitmap_set() instead of set_bit() in numa_add() routine.
- removed call to bitmak_zero() since bitmap_new() also zeros' the bitmap.
- Rebased to the latest qemu.
On Fri, 3 Aug 2012 14:31:22 -0300, Marcelo Tosatti mtosa...@redhat.com wrote:
On Fri, Aug 03, 2012 at 11:25:44AM +0530, Nikunj A Dadhania wrote:
On Thu, 2 Aug 2012 16:56:28 -0300, Marcelo Tosatti mtosa...@redhat.com
wrote:
+ case MSR_KVM_VCPU_STATE:
+
On Jul 9, 2012, at 7:58 AM, Varun Sethi wrote:
Merge the 32 bit cpu setup code for e500mc/e5500 and define the cpu_restore
routine (for e5500/e6500) only for the 64 bit case. The cpu_restore routine
is used in the 64 bit case for setting up the secondary cores.
Signed-off-by: Varun Sethi
On Jul 9, 2012, at 8:01 AM, Varun Sethi wrote:
For the 64 bit case separate out e5500 cpu_setup and cpu_restore functions.
The cpu_setup function (for the primary core) is passed the cpu_spec pointer,
which is not there in case of the cpu_restore function. Also, in our case
we will have to
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Friday, August 03, 2012 10:04 PM
To: Sethi Varun-B16395
Cc: ag...@suse.de; b...@kernel.crashing.org; linuxppc-
d...@lists.ozlabs.org; kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 2/4] powerpc/booke: Merge