From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: windows PIO question
Date: Sun, 5 Feb 2012 22:01:26 +0100 [thread overview]
Message-ID: <20120205210126.GA2321@nik-comp.lan> (raw)
In-Reply-To: <4F2E9BFF.1050700@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3782 bytes --]
> Not all PIO operations are DMA. Provide a trace and we can look.
Hi,
here's snippet:
qemu-kvm-16441 [000] 12887154.698329: kvm_pio: pio_read at 0xc002 size 1 count 1
qemu-kvm-16441 [000] 12887154.698331: kvm_userspace_exit: reason KVM_EXIT_IO (2)
qemu-kvm-16441 [000] 12887154.698331: kvm_fpu: unload
qemu-kvm-16441 [000] 12887154.698337: kvm_entry: vcpu 1
qemu-kvm-16441 [000] 12887154.698338: kvm_exit: [FAILED TO PARSE] exit_reason=30 guest_rip=0xfffff88000dabca3 isa=1 info1=3221356552 info2=0
qemu-kvm-16441 [000] 12887154.698339: kvm_emulate_insn: [FAILED TO PARSE] rip=18446735827386678435 csbase=0 len=1 insn=<EC><C3><CC><CC><CC><CC><CC><CC><CC>^O<B7><D1>f<ED><C3> flags=9 failed=0
qemu-kvm-16441 [000] 12887154.698340: kvm_pio: pio_read at 0xc002 size 1 count 1
qemu-kvm-16441 [000] 12887154.698340: kvm_userspace_exit: reason KVM_EXIT_IO (2)
qemu-kvm-16441 [000] 12887154.698343: kvm_entry: vcpu 1
qemu-kvm-16441 [000] 12887154.698344: kvm_exit: [FAILED TO PARSE] exit_reason=30 guest_rip=0xfffff88000dabdbd isa=1 info1=3221225472 info2=0
qemu-kvm-16441 [000] 12887154.698345: kvm_pio: pio_write at 0xc000 size 1 count 1
qemu-kvm-16441 [000] 12887154.698346: kvm_userspace_exit: reason KVM_EXIT_IO (2)
qemu-kvm-16441 [000] 12887154.698348: kvm_entry: vcpu 1
qemu-kvm-16441 [000] 12887154.698349: kvm_exit: [FAILED TO PARSE] exit_reason=30 guest_rip=0xfffff88000dabdbd isa=1 info1=3221356544 info2=0
qemu-kvm-16441 [000] 12887154.698349: kvm_pio: pio_write at 0xc002 size 1 count 1
qemu-kvm-16441 [000] 12887154.698350: kvm_userspace_exit: reason KVM_EXIT_IO (2)
qemu-kvm-16441 [000] 12887154.698352: kvm_entry: vcpu 1
qemu-kvm-16441 [000] 12887154.698353: kvm_exit: [FAILED TO PARSE] exit_reason=30 guest_rip=0xfffff88000dabca3 isa=1 info1=32964616 info2=0
qemu-kvm-16441 [000] 12887154.698354: kvm_emulate_insn: [FAILED TO PARSE] rip=18446735827386678435 csbase=0 len=1 insn=<EC><C3><CC><CC><CC><CC><CC><CC><CC>^O<B7><D1>f<ED><C3> flags=9 failed=0
qemu-kvm-16441 [000] 12887154.698354: kvm_pio: pio_read at 0x1f7 size 1 count 1
qemu-kvm-16441 [000] 12887154.698355: kvm_userspace_exit: reason KVM_EXIT_IO (2)
qemu-kvm-16441 [000] 12887154.698357: kvm_set_irq: gsi 14 level 0 source 0
qemu-kvm-16441 [000] 12887154.698358: kvm_pic_set_irq: chip 1 pin 6 (edge|masked)
qemu-kvm-16441 [000] 12887154.698358: kvm_ioapic_set_irq: pin 14 dst 3 vec=97 (LowPrio|logical|edge)
qemu-kvm-16441 [000] 12887154.698360: kvm_entry: vcpu 1
qemu-kvm-16441 [000] 12887154.698362: kvm_exit: [FAILED TO PARSE] exit_reason=30 guest_rip=0xfffff88000dabca3 isa=1 info1=32964616 info2=0
qemu-kvm-16441 [000] 12887154.698363: kvm_emulate_insn: [FAILED TO PARSE] rip=18446735827386678435 csbase=0 len=1 insn=<EC><C3><CC><CC><CC><CC><CC><CC><CC>^O<B7><D1>f<ED><C3> flags=9 failed=0
qemu-kvm-16441 [000] 12887154.698363: kvm_pio: pio_read at 0x1f7 size 1 count 1
n.
>
> --
> error compiling committee.c: too many arguments to function
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-05 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 21:16 windows PIO question Nikola Ciprich
2012-02-05 15:10 ` Avi Kivity
2012-02-05 21:01 ` Nikola Ciprich [this message]
2012-02-06 9:50 ` Avi Kivity
2012-02-07 8:25 ` Nikola Ciprich
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=20120205210126.GA2321@nik-comp.lan \
--to=nikola.ciprich@linuxbox.cz \
--cc=avi@redhat.com \
--cc=kvm@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;
as well as URLs for NNTP newsgroup(s).