From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: kvm-ppc@vger.kernel.org
Subject: Re: Does KVM support the P.A. Semi PA6T cpu?
Date: Fri, 30 May 2014 17:38:58 +0000 [thread overview]
Message-ID: <5388C232.1080100@xenosoft.de> (raw)
In-Reply-To: <53511C7B.5010208@xenosoft.de>
On 30.05.2014 17:46, Alexander Graf wrote:
>
>>> This should do the trick. Output will be in dmesg:
>>>
>>> diff --git a/arch/powerpc/kvm/book3s_32_mmu.c
>>> b/arch/powerpc/kvm/book3s_32_mmu.c
>>> index 93503bb..939b14f 100644
>>> --- a/arch/powerpc/kvm/book3s_32_mmu.c
>>> +++ b/arch/powerpc/kvm/book3s_32_mmu.c
>>> @@ -27,8 +27,8 @@
>>> #include <asm/kvm_ppc.h>
>>> #include <asm/kvm_book3s.h>
>>>
>>> -/* #define DEBUG_MMU */
>>> -/* #define DEBUG_MMU_PTE */
>>> +#define DEBUG_MMU
>>> +#define DEBUG_MMU_PTE
>>> /* #define DEBUG_MMU_PTE_IP 0xfff14c40 */
>>>
>>> #ifdef DEBUG_MMU
>> Hi Alex,
>>
>> Unfortunately, the KVM modul doesn't compile with DEBUG_MMU.
>>
>> Kernel 3.14.4:
>>
>> make modules
>> CHK include/config/kernel.release
>> CHK include/generated/uapi/linux/version.h
>> CHK include/generated/utsrelease.h
>> CALL scripts/checksyscalls.sh
>> AS [M] arch/powerpc/kvm/fpu.o
>> CC [M] arch/powerpc/kvm/book3s_paired_singles.o
>> CC [M] arch/powerpc/kvm/book3s_pr.o
>> CC [M] arch/powerpc/kvm/book3s_pr_papr.o
>> CC [M] arch/powerpc/kvm/book3s_emulate.o
>> AS [M] arch/powerpc/kvm/book3s_interrupts.o
>> CC [M] arch/powerpc/kvm/book3s_mmu_hpte.o
>> CC [M] arch/powerpc/kvm/book3s_64_mmu_host.o
>> CC [M] arch/powerpc/kvm/book3s_64_mmu.o
>> CC [M] arch/powerpc/kvm/book3s_32_mmu.o
>> arch/powerpc/kvm/book3s_32_mmu.c: In function
>> ‘kvmppc_mmu_book3s_32_get_pteg’:
>> arch/powerpc/kvm/book3s_32_mmu.c:133:2: error: ‘struct
>> kvmppc_vcpu_book3s’ has no member named
>
> Och jetzt komm - das bisschen C um den zu fixen wirst du doch noch
> schaffen, oder? ;)
>
>
Huch, Deutsch. Bestimmt aus Nürnberg. :D Meine Lieblingsstadt. ;-) I
have solved the problem above.
Dmesg logs:
watch -n 0 "dmesg" > dmesg_mol_mac_os_x_tiger.txt
watch -n 0 "dmesg" > dmesg_mol_mac_os_x_jaguar.txt
http://forum.hyperion-entertainment.biz/download/file.php?id\x1215
http://forum.hyperion-entertainment.biz/download/file.php?id\x1216
more dmesg_mol_mac_os_x_tiger.txt
I hope you can fix the problem.
-- Christian
next prev parent reply other threads:[~2014-05-30 17:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 12:37 Does KVM support the P.A. Semi PA6T cpu? Christian Zigotzky
2014-04-18 15:35 ` Alexander Graf
2014-04-18 22:10 ` Christian Zigotzky
2014-04-18 22:46 ` Alexander Graf
2014-04-19 11:40 ` Christian Zigotzky
2014-04-19 12:36 ` Christian Zigotzky
2014-04-19 15:08 ` Christian Zigotzky
2014-04-19 19:56 ` Christian Zigotzky
2014-04-21 15:45 ` Christian Zigotzky
2014-04-26 22:11 ` Christian Zigotzky
2014-04-27 17:41 ` Christian Zigotzky
2014-04-27 17:47 ` Alexander Graf
2014-04-28 14:19 ` Christian Zigotzky
2014-04-28 19:03 ` Christian Zigotzky
2014-04-29 9:14 ` Alexander Graf
2014-05-29 23:50 ` Christian Zigotzky
2014-05-30 7:49 ` Alexander Graf
2014-05-30 11:39 ` Christian Zigotzky
2014-05-30 12:21 ` Alexander Graf
2014-05-30 12:42 ` Christian Zigotzky
2014-05-30 12:47 ` Alexander Graf
2014-05-30 15:44 ` Christian Zigotzky
2014-05-30 17:38 ` Christian Zigotzky [this message]
2014-06-10 10:39 ` Christian Zigotzky
2014-06-10 13:56 ` 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=5388C232.1080100@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=kvm-ppc@vger.kernel.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