From: Avi Kivity <avi@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH kvm-unit-tests 07/10] Correct the tss size
Date: Wed, 25 Aug 2010 15:45:54 +0300 [thread overview]
Message-ID: <4C751082.8040007@redhat.com> (raw)
In-Reply-To: <1721172229.518061282739248257.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
On 08/25/2010 03:27 PM, Jason Wang wrote:
> ----- "Avi Kivity"<avi@redhat.com> wrote:
>
>> On 08/25/2010 12:40 PM, Jason Wang wrote:
>>> ----- "Avi Kivity"<avi@redhat.com> wrote:
>>>
>>>> On 08/24/2010 04:47 PM, Jason Wang wrote:
>>>>> TSS size should be 104 byte.
>>>>>
>>>>> Signed-off-by: Jason Wang<jasowang@redhat.com>
>>>>> ---
>>>>> x86/cstart64.S | 2 +-
>>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>
>>>>> diff --git a/x86/cstart64.S b/x86/cstart64.S
>>>>> index 5d358ad..b871153 100644
>>>>> --- a/x86/cstart64.S
>>>>> +++ b/x86/cstart64.S
>>>>> @@ -69,7 +69,7 @@ tss:
>>>>> .long 0
>>>>> .quad ring0stacktop - i * 4096
>>>> ring 0 stack
>>>>
>>>>> .quad 0, 0, 0
>>>> rings 1, 2, 3 stack
>>> Hello avi:
>>>
>>> Rechek with the manual, there's no filed of RSP3. So this patch may
>>> make sense.
>> That is true. But please redo it to remove one 0 from the line above,
>>
>> not from the IST.
>>
>>> But unfortunately it breaks 64bit vmexit test. Triple
>>> fault happens in setup_args(). Any suggestions or is there any thing
>> I
>>> missed?
>> No idea. Can you post an ftrace of the crash?
>>
> The trace before triple fault:
>
> ......
> qemu-kvm-8101 [002] 243.138507: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138508: kvm_exit: reason IO_INSTRUCTION rip 0x400e5f
> qemu-kvm-8101 [002] 243.138508: kvm_pio: pio_read at 0x510 size 2 count 1
> qemu-kvm-8101 [002] 243.138512: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138513: kvm_exit: reason IO_INSTRUCTION rip 0x400e71
> qemu-kvm-8101 [002] 243.138514: kvm_emulate_insn: 0:400e71: ec (prot64)
> qemu-kvm-8101 [002] 243.138515: kvm_pio: pio_write at 0x511 size 1 count 1
> qemu-kvm-8101 [002] 243.138519: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138520: kvm_exit: reason IO_INSTRUCTION rip 0x400e71
> qemu-kvm-8101 [002] 243.138521: kvm_emulate_insn: 0:400e71: ec (prot64)
> qemu-kvm-8101 [002] 243.138521: kvm_pio: pio_write at 0x511 size 1 count 1
> qemu-kvm-8101 [002] 243.138525: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138526: kvm_exit: reason CPUID rip 0x400ff7
> qemu-kvm-8101 [002] 243.138526: kvm_cpuid: func 1 rax 6d3 rbx 800 rcx 80002001 rdx 78bfbfd
> qemu-kvm-8101 [002] 243.138527: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138528: kvm_exit: reason EXCEPTION_NMI rip 0x400271
> qemu-kvm-8101 [002] 243.138528: kvm_page_fault: address 40f3a0 error_code b
> qemu-kvm-8101 [002] 243.138530: kvm_entry: vcpu 0
> qemu-kvm-8101 [002] 243.138531: kvm_exit: reason TRIPLE_FAULT rip 0x400c15
>
What's the corresponding disassembly?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-08-25 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1917811696.509261282728232368.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-08-25 9:40 ` [PATCH kvm-unit-tests 07/10] Correct the tss size Jason Wang
2010-08-25 9:55 ` Avi Kivity
2010-08-25 12:27 ` Jason Wang
2010-08-25 12:45 ` Avi Kivity [this message]
2010-08-25 13:00 ` Jason Wang
2010-08-25 13:11 ` Avi Kivity
[not found] <1014013070.604691282806259198.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-08-26 7:05 ` Jason Wang
2010-08-26 8:06 ` Avi Kivity
2010-08-24 13:46 [PATCH kvm-unit-tests 00/10] Minor cleanup and fix for 32bit test Jason Wang
2010-08-24 13:47 ` [PATCH kvm-unit-tests 07/10] Correct the tss size Jason Wang
2010-08-24 13:57 ` Avi Kivity
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=4C751082.8040007@redhat.com \
--to=avi@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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