From: Jason Wang <jasowang@redhat.com>
To: P J P <ppandit@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.5] eepro100: Prevent two endless loops
Date: Wed, 25 Nov 2015 11:08:36 +0800 [thread overview]
Message-ID: <56552634.9060805@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1511201647500.22982@wniryva>
On 11/20/2015 07:27 PM, P J P wrote:
> +-- On Fri, 20 Nov 2015, Stefan Weil wrote --+
> | include/hw/pci/pci.h: static inline uint##_bits##_t
> | ld##_l##_pci_dma(PCIDevice *dev, \
>
> I see.
>
> | Is there an ideal count? If it is too low, it might break some use cases.
> | If it is too high, it will take longer until the loop is finished.
>
> -> https://url.corp.redhat.com/8255x-manual-pdf
>
> I tried to look trough the 8255x manual above, it does not have a specific
> value for the count, as it's a linked list of command blocks.
>
>
> | I don't think EEPRO100 emulation is used in critical production
> | applications. Therefore a lower value and a debug message when this value is
> | exceeded might be helpful to find out which lowest value is acceptable. If
> | you want to avoid this risk, the value should be set to 256, 10000, 65536 or
> | any other higher value. Feel free to change this when you apply the patch.
>
> I guess Jason would be best to decide that.
>
>
> Thank you.
> --
> - P J P
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
>
Apply the patch as is. We could enlarge the limitation if we find it was
too small in the future.
Thanks
prev parent reply other threads:[~2015-11-25 3:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 7:42 [Qemu-devel] [PATCH for-2.5] eepro100: Prevent two endless loops Stefan Weil
2015-11-20 8:39 ` P J P
2015-11-20 8:52 ` Stefan Weil
2015-11-20 11:27 ` P J P
2015-11-25 3:08 ` Jason Wang [this message]
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=56552634.9060805@redhat.com \
--to=jasowang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.