Hi Paolo,
On Mon, 8 Feb 2021 06:48:32 +1100 Stephen Rothwell
wrote:
>
> On Fri, 5 Feb 2021 11:08:39 +0100 Paolo Bonzini wrote:
> >
> > On 05/02/21 06:02, Stephen Rothwell wrote:
> > >
> > > After merging the kvm tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like
Thanks a lot for reporting this, Stephen. Just sent out a patch
to fix it in kvmgt.
B.R.
Yu
On Mon, Feb 08, 2021 at 04:33:08PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
>
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
drivers/gpu/drm/i915/gvt/kvmgt.c: In function 'kvmgt_page_track_add':
drivers/gpu/drm/i915/gvt/kvmgt.c:1706:12: error: passing argument 1 of
'spin_lock' from incompatible pointer type
Hi Paolo,
On Fri, 5 Feb 2021 11:08:39 +0100 Paolo Bonzini wrote:
>
> On 05/02/21 06:02, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the kvm tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > ERROR: modpost: ".follow_pte"
On 05/02/21 06:02, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: modpost: ".follow_pte" [arch/powerpc/kvm/kvm.ko] undefined!
Caused by commit
bd2fae8da794 ("KVM: do not assume PTE is writable after
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: modpost: ".follow_pte" [arch/powerpc/kvm/kvm.ko] undefined!
Caused by commit
bd2fae8da794 ("KVM: do not assume PTE is writable after follow_pfn")
follow_pte is not EXPORTed.
I
Hi all,
On Fri, 17 Jul 2020 15:57:01 +1000 Stephen Rothwell
wrote:
>
> After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/kernel/kvm.c: In function '__sysvec_kvm_asyncpf_interrupt':
> arch/x86/kernel/kvm.c:275:13: error: implicit
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kernel/kvm.c: In function '__sysvec_kvm_asyncpf_interrupt':
arch/x86/kernel/kvm.c:275:13: error: implicit declaration of function
'idtentry_enter_cond_rcu'; did you mean
Hi all,
On Thu, 21 May 2020 16:28:54 +1000 Stephen Rothwell
wrote:
>
> After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> arch/x86/kvm/svm/svm.c: In function 'kvm_machine_check':
> arch/x86/kvm/svm/svm.c:1834:2: error: too many arguments to
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kvm/svm/svm.c: In function 'kvm_machine_check':
arch/x86/kvm/svm/svm.c:1834:2: error: too many arguments to function
'do_machine_check'
1834 | do_machine_check(, 0);
|
On 19/02/19 16:36, Sean Christopherson wrote:
> On Mon, Feb 18, 2019 at 02:42:00PM +1100, Stephen Rothwell wrote:
>> Hi all,
>
> ...
>
>> Caused by commits
>>
>> 1561fcbc8e16 ("KVM: x86: Explicitly #define the VCPU_REGS_* indices")
>> a46e726511f4 ("KVM: VMX: Move vCPU-run code to a proper
On Mon, Feb 18, 2019 at 02:42:00PM +1100, Stephen Rothwell wrote:
> Hi all,
...
> Caused by commits
>
> 1561fcbc8e16 ("KVM: x86: Explicitly #define the VCPU_REGS_* indices")
> a46e726511f4 ("KVM: VMX: Move vCPU-run code to a proper assembly routine")
>
> It looks like a file was not git
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
In file included from include/linux/kvm_host.h:38,
from arch/x86/kvm/../../../virt/kvm/coalesced_mmio.c:14:
arch/x86/include/asm/kvm_host.h:38:10: fatal error:
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kvm/vmx/nested.c: In function 'prepare_vmcs02_full':
arch/x86/kvm/vmx/nested.c:2242:6: error: implicit declaration of function
'kvm_mpx_supported'; did you mean 'vmx_mpx_supported'?
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kvm/x86.c: In function 'kvm_pv_clock_pairing':
arch/x86/kvm/x86.c:6157:2: error: unknown type name 'cycle_t'
cycle_t cycle;
^
arch/x86/kvm/x86.c:6163:42: error: passing argument 2 of
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kvm/x86.c: In function 'kvm_pv_clock_pairing':
arch/x86/kvm/x86.c:6157:2: error: unknown type name 'cycle_t'
cycle_t cycle;
^
arch/x86/kvm/x86.c:6163:42: error: passing argument 2 of
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kernel/kvm.c: In function '__kvm_vcpu_is_preempted':
arch/x86/kernel/kvm.c:596:14: error: 'struct kvm_steal_time' has no member
named 'preempted'
return !!src->preempted;
Hi all,
After merging the kvm tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
arch/x86/kernel/kvm.c: In function '__kvm_vcpu_is_preempted':
arch/x86/kernel/kvm.c:596:14: error: 'struct kvm_steal_time' has no member
named 'preempted'
return !!src->preempted;
On 08/09/2015 04:10, Wanpeng Li wrote:
>
> I miss place the trace codes under CONFIG_KVM_ASYNC_PF, the patch in the
> attachment rewrite the commit and fix it. Sorry for that.
Thanks. I cannot rewind kvm/next, so I committed just the incremental change:
diff --git
On 08/09/2015 04:10, Wanpeng Li wrote:
>
> I miss place the trace codes under CONFIG_KVM_ASYNC_PF, the patch in the
> attachment rewrite the commit and fix it. Sorry for that.
Thanks. I cannot rewind kvm/next, so I committed just the incremental change:
diff --git
Hi Paolo, Stephen,
On 9/8/15 9:35 AM, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1931:2: error: implicit
declaration of function
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1931:2: error: implicit
declaration of function
Hi Paolo, Stephen,
On 9/8/15 9:35 AM, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'grow_halt_poll_ns':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/05/2015 09:36, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
> arch/x86/kvm/cpuid.c:98:2:
* Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
> arch/x86/kvm/cpuid.c:98:2: error: implicit declaration of function
> 'use_eager_fpu'
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
arch/x86/kvm/cpuid.c:98:2: error: implicit declaration of function
'use_eager_fpu' [-Werror=implicit-function-declaration]
* Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
arch/x86/kvm/cpuid.c:98:2: error: implicit declaration of function
'use_eager_fpu'
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
arch/x86/kvm/cpuid.c:98:2: error: implicit declaration of function
'use_eager_fpu' [-Werror=implicit-function-declaration]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/05/2015 09:36, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/kvm/cpuid.c: In function 'kvm_update_cpuid':
arch/x86/kvm/cpuid.c:98:2: error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/2014 07:19, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kvm tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "get_xsave_addr" [arch/x86/kvm/kvm.ko] undefined!
>
> Caused by commit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/11/2014 07:19, Stephen Rothwell wrote:
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: get_xsave_addr [arch/x86/kvm/kvm.ko] undefined!
Caused by commit 1d7fe1d1fb18 (KVM:
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "get_xsave_addr" [arch/x86/kvm/kvm.ko] undefined!
Caused by commit 1d7fe1d1fb18 ("KVM: x86: support XSAVES usage in the
host").
I have used the kvm tree from next-20141121 for today.
--
Hi all,
After merging the kvm tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: get_xsave_addr [arch/x86/kvm/kvm.ko] undefined!
Caused by commit 1d7fe1d1fb18 (KVM: x86: support XSAVES usage in the
host).
I have used the kvm tree from next-20141121 for today.
--
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from /scratch/sfr/next/include/linux/preempt.h:10:0,
from /scratch/sfr/next/include/linux/preempt_mask.h:4,
from
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from /scratch/sfr/next/include/linux/preempt.h:10:0,
from /scratch/sfr/next/include/linux/preempt_mask.h:4,
from
Hi all,
After merging the kvm tree, today's linux-next build (20140311)
failed like this:
/home/broonie/next/next/arch/x86/kvm/vmx.c: In function
'nested_vmx_setup_ctls_msrs':
/home/broonie/next/next/arch/x86/kvm/vmx.c:2292:2: error: implicit declaration
of function 'vmx_mpx_supported'
Hi all,
After merging the kvm tree, today's linux-next build (20140311)
failed like this:
/home/broonie/next/next/arch/x86/kvm/vmx.c: In function
'nested_vmx_setup_ctls_msrs':
/home/broonie/next/next/arch/x86/kvm/vmx.c:2292:2: error: implicit declaration
of function 'vmx_mpx_supported'
Hi all,
On Fri, 10 Jan 2014 14:00:43 +1100 Stephen Rothwell
wrote:
>
> After merging the kvm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_on_spin':
>
Hi all,
On Fri, 10 Jan 2014 14:00:43 +1100 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_on_spin':
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_on_spin':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1807:4: error: implicit
declaration of function
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_vcpu_on_spin':
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:1807:4: error: implicit
declaration of function
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/built-in.o: In function `.kvmppc_h_enter':
(.text+0x2494): undefined reference to `.gfn_to_hva_memslot'
Presumably caused by commit 4d8b81abc47b ("KVM: introduce readonly
Hi all,
After merging the kvm tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/kvm/built-in.o: In function `.kvmppc_h_enter':
(.text+0x2494): undefined reference to `.gfn_to_hva_memslot'
Presumably caused by commit 4d8b81abc47b (KVM: introduce readonly
44 matches
Mail list logo
