From: "Richard W.M. Jones" <rjones@redhat.com>
To: Adam Hoka <adam.hoka@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] i6300esb: fix reading config registers and accept writes of all length
Date: Tue, 2 Dec 2014 18:41:45 +0000 [thread overview]
Message-ID: <20141202184145.GC15695@redhat.com> (raw)
In-Reply-To: <547E042F.7010201@gmail.com>
On Tue, Dec 02, 2014 at 07:25:51PM +0100, Adam Hoka wrote:
> On 11/30/2014 11:31 PM, Richard W.M. Jones wrote:
> >http://git.annexia.org/?p=watchdog-test-framework.git;a=summary
> >
> >Rich.
>
> Thanks for the feedback. I guess I could test it on Linux. Should I
> just run this utility?
The idea of the watchdog test framework is to make it easy to test the
watchdog, compared to configuring and using the watchdog daemon. Read
the 'README' file first.
> What's wrong with the Intel/Win driver?
Hah hah, where to start? Completely broken would be a good
executive level description of it. Some of the problems we found:
- It assumes that the card is located in a particular PCI slot (slot
0 IIRC), and if it's not then it randomly writes to physical memory
addresses >= 0x1_0000_0000. In other words, it ignores boring old
stuff like PCI config.
- It's 32 bit / old Windows only.
- No source.
- No watchdog framework, so it's not actually useful in the real
world. (Windows itself does have a watchdog framework, but not in
consumer/server versions.)
> BTW, could you ever find some documentation on where the hell is the
> IRQ line is connected on real HW?
The only docs I'm aware of are the Intel ones, section 16 of:
http://www.intel.co.uk/content/dam/doc/datasheet/6300esb-io-controller-hub-datasheet.pdf
plus of course the Linux driver.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
prev parent reply other threads:[~2014-12-02 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 13:42 [Qemu-devel] [PATCH] i6300esb: fix reading config registers and accept writes of all length Adam Hoka
2014-11-30 22:31 ` Richard W.M. Jones
2014-12-02 18:25 ` Adam Hoka
2014-12-02 18:41 ` Richard W.M. Jones [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=20141202184145.GC15695@redhat.com \
--to=rjones@redhat.com \
--cc=adam.hoka@gmail.com \
--cc=qemu-devel@nongnu.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).