From: Li Qiang <liq3ea@gmail.com>
To: Peter Xu <peterx@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Jiri Slaby" <jslaby@suse.cz>, "Li Qiang" <liq3ea@163.com>,
"Qemu Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes
Date: Sat, 11 May 2019 08:40:21 +0800 [thread overview]
Message-ID: <CAKXe6S+8yL7=trJqcXmCe+Z+mNabBP-6q3bzW2zEyoen=wM0Kw@mail.gmail.com> (raw)
In-Reply-To: <20190510235318.GO18465@xz-x1>
Peter Xu <peterx@redhat.com> 于2019年5月11日周六 上午7:53写道：
> On Fri, May 10, 2019 at 09:43:46AM -0700, Li Qiang wrote:
> > Recently I am considering write a driver for edu device.
>
> I don't know why you wanted to write it, but there's one (though I
> don't even remember whether it's working or not)...
>
>
This is a simple device, once I used it to debug and make clear some
hardware-related stuff of PCI device,
such as PCI interrupt routing, interrupt linking device, interrupt raise
and the process of injecting.
I think if there is a driver, I can do this inspection more easily.
>
> https://github.com/xzpeter/clibs/blob/master/gpl/linux_kernel/edu_device_driver/edu.c
>
>
Great!
Thanks,
Li Qiang
> Regards,
>
> --
> Peter Xu
>
next prev parent reply other threads:[~2019-05-11 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:43 [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 1/3] edu: mmio: allow 64-bit access Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 2/3] edu: mmio: allow 64-bit access in read dispatch Li Qiang
2019-05-10 16:43 ` [Qemu-devel] [PATCH v4 3/3] edu: uses uint64_t in dma operation Li Qiang
2019-05-22 11:01 ` Philippe Mathieu-Daudé
2019-05-10 23:53 ` [Qemu-devel] [PATCH v4 0/3] hw: edu: some fixes Peter Xu
2019-05-11 0:40 ` Li Qiang [this message]
2019-05-21 13:30 ` Li Qiang
2019-05-22 8:29 ` Paolo Bonzini
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='CAKXe6S+8yL7=trJqcXmCe+Z+mNabBP-6q3bzW2zEyoen=wM0Kw@mail.gmail.com' \
--to=liq3ea@gmail.com \
--cc=jslaby@suse.cz \
--cc=liq3ea@163.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@redhat.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 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.