From: Paolo Bonzini <pbonzini@redhat.com>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Bin Meng <bin.meng@windriver.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] target/i386: seg_helper: Correct segement selector nullification in the RET/IRET helper
Date: Tue, 17 Nov 2020 12:06:36 +0100 [thread overview]
Message-ID: <17dc8a7c-d72d-09b0-51df-ff907c1dcce2@redhat.com> (raw)
In-Reply-To: <CAEUhbmWPi=4u8y0U0Py7rxyFVkD5gqkDQsze39XjPaXsADnJtg@mail.gmail.com>
On 17/11/20 11:08, Bin Meng wrote:
>> I see. Is there any chance you could write a testcase for
>> kvm-unit-tests? Or just explain how to write such a test, and then I
>> can write it myself; it's not clear to me how the guest can observe the
>> base and limit of a non-present segment.
>
> I am not familiar with kvm-unit-test. The original issue cannot be
> reproduced with a KVM enabled QEMU as the codes-in-flaw is in the
> emulation path.
kvm-unit-tests, despite the name, is a set generic tests for CPU
behavior; it works with other accelerators that QEMU supports including
the emulation path. You can find it at
https://gitlab.com/kvm-unit-tests/kvm-unit-tests.
If you explain in enough detail how VxWorks triggers the bug, I can take
care of writing the test.
Paolo
next prev parent reply other threads:[~2020-11-17 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 9:56 [PATCH v2] target/i386: seg_helper: Correct segement selector nullification in the RET/IRET helper Bin Meng
2020-11-13 10:18 ` Paolo Bonzini
2020-11-13 10:23 ` Bin Meng
2020-11-13 10:39 ` Paolo Bonzini
2020-11-17 10:08 ` Bin Meng
2020-11-17 11:06 ` Paolo Bonzini [this message]
2020-11-24 6:09 ` Bin Meng
2020-11-16 12:48 ` Philippe Mathieu-Daudé
2020-11-30 14:01 ` Bin Meng
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=17dc8a7c-d72d-09b0-51df-ff907c1dcce2@redhat.com \
--to=pbonzini@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bmeng.cn@gmail.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).