From: Jason Wang <jasowang@redhat.com>
To: Qinghao Tang <luodalongde@gmail.com>
Cc: P J P <ppandit@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH] eepro100: prevent an infinite loop over same command block
Date: Tue, 20 Oct 2015 11:04:43 +0800 [thread overview]
Message-ID: <5625AF4B.9060409@redhat.com> (raw)
In-Reply-To: <CAFEAcA_D3kKnWZCFJA-eHwt0kvFHCcU3nOvDwd8escfDsWtigQ@mail.gmail.com>
On 10/17/2015 07:35 PM, Peter Maydell wrote:
> On 16 October 2015 at 22:37, Stefan Weil <sw@weilnetz.de> wrote:
>> Maybe real hardware will run an endless loop?
>> Or the "endless" loop is terminated because the driver
>> changes the link while the loop is running?
>>
>> The goal of eepro100.c should be emulation of the
>> real hardware, even of a potential design weakness.
> I agree in general, but we need to be sure that if we're
> letting the guest put a device into an infinite loop this
> doesn't lock up the whole VM (ie preventing the user
> from using the qemu monitor or otherwise rebooting it).
>
> thanks
> -- PMM
>
Yes, so the reproducer needs to be tested on real hardware.
Qinghao:
Any chance to test the reproducer on real e100? If not, I will try to
find one to test.
Thanks
next prev parent reply other threads:[~2015-10-20 3:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:12 [Qemu-devel] [PATCH] eepro100: prevent an infinite loop over same command block P J P
2015-10-16 12:41 ` Paolo Bonzini
2015-10-16 17:19 ` P J P
2015-10-16 21:37 ` Stefan Weil
2015-10-17 11:25 ` P J P
2015-10-17 11:35 ` Peter Maydell
2015-10-20 3:04 ` Jason Wang [this message]
2015-10-20 3:10 ` max
2015-10-20 3:02 ` Jason Wang
2015-11-03 18:49 ` P J P
2015-11-04 3:31 ` Jason Wang
2015-11-20 2:43 ` Qinghao Tang
2015-11-20 6:10 ` P J P
2015-11-20 6:29 ` Qinghao Tang
2015-11-20 7:23 ` P J P
2015-11-20 7:47 ` Stefan Weil
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=5625AF4B.9060409@redhat.com \
--to=jasowang@redhat.com \
--cc=luodalongde@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).