From: Paolo Bonzini <pbonzini@redhat.com>
To: "Salva Peiró" <speirofr@gmail.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] memory: Add function pointers checks to memory_region_read/write()
Date: Tue, 8 Sep 2015 10:55:56 +0200 [thread overview]
Message-ID: <55EEA29C.2010509@redhat.com> (raw)
In-Reply-To: <CAJpd-bGU3b-aF4yD==OqOUduCbSVO_D00ZKpWDOSJp31-2rwAw@mail.gmail.com>
On 08/09/2015 08:51, Salva Peiró wrote:
> Rigth, I should have started by providing the scenario where the fault occurs.
> The problem occurs performing a writeb to the BAR0 of device 1033:194.
> That is PCI_DEVICE_ID_NEC_UPD720200 0x0194 at hw/usb/hcd-xhci.c
>
> I've attached tests/nec-usb-xhci-test.c that reproduces the scenario.
Thanks, this is a good addition. Please submit a fix to hcd-xhci.c and
the test case!
Paolo
next prev parent reply other threads:[~2015-09-08 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 17:37 [Qemu-devel] [PATCH] memory: Add function pointers checks to memory_region_read/write() Salva Peiró
2015-09-07 10:27 ` Paolo Bonzini
2015-09-08 6:51 ` Salva Peiró
2015-09-08 8:55 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-28 7:13 [Qemu-devel] " Salva Peiró
2015-07-28 7:13 ` [Qemu-devel] [PATCH] " Salva Peiró
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=55EEA29C.2010509@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=speirofr@gmail.com \
/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).