From: Marcel Apfelbaum <marcel.a@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Anthony Liguori" <aliguori@us.ibm.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 2/3] hw/pci: add MemoryRegion ops for unassigned pci addresses
Date: Mon, 02 Sep 2013 18:46:44 +0300 [thread overview]
Message-ID: <1378136804.2640.36.camel@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA9KKgyXw3JRSQ2hp9uA4PWrt7Lha4cFHW_xv7RRts5F5A@mail.gmail.com>
On Mon, 2013-09-02 at 15:42 +0100, Peter Maydell wrote:
> On 2 September 2013 15:13, Marcel Apfelbaum <marcel.a@redhat.com> wrote:
> > +const MemoryRegionOps pci_unassigned_mem_ops = {
> > + .valid.accepts = pci_unassigned_mem_accepts,
> > + .endianness = DEVICE_NATIVE_ENDIAN,
> > +};
>
> This is wrong -- you want reads and writes to result in
> your PCI-spec-defined behaviour, but if you provide
> an accepts callback and it returns false then you get
> "machine dependent behaviour such as a machine check
> exception". What you want is to provide .read and .write
> callbacks which behave as the PCI spec mandates.
That makes sense. It was already a bug.Thanks!
>
> Also this should probably be static, not global, and you
If it will be implemented in the "pci core layer", sure
Marcel
> should put it in the same patch as the one which actually
> creates the memory region.
>
> -- PMM
>
next prev parent reply other threads:[~2013-09-02 15:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 14:13 [Qemu-devel] [PATCH RFC 0/3] pci: complete master abort protocol Marcel Apfelbaum
2013-09-02 14:13 ` [Qemu-devel] [PATCH RFC 1/3] memory: allow MemoryRegion's priority field to accept negative values Marcel Apfelbaum
2013-09-02 14:38 ` Peter Maydell
2013-09-02 14:46 ` Marcel Apfelbaum
2013-09-09 12:16 ` Marcel Apfelbaum
2013-09-02 14:13 ` [Qemu-devel] [PATCH RFC 2/3] hw/pci: add MemoryRegion ops for unassigned pci addresses Marcel Apfelbaum
2013-09-02 14:42 ` Peter Maydell
2013-09-02 15:46 ` Marcel Apfelbaum [this message]
2013-09-02 14:48 ` Michael S. Tsirkin
2013-09-02 14:51 ` Marcel Apfelbaum
2013-09-02 14:13 ` [Qemu-devel] [PATCH RFC 3/3] hw/pci-host: catch acesses to " Marcel Apfelbaum
2013-09-02 14:39 ` Peter Maydell
2013-09-02 15:42 ` Marcel Apfelbaum
2013-09-02 15:48 ` Andreas Färber
2013-09-02 15:53 ` Peter Maydell
2013-09-02 15:58 ` Peter Maydell
2013-09-02 16:00 ` Michael S. Tsirkin
2013-09-02 16:05 ` Peter Maydell
2013-09-02 16:17 ` Michael S. Tsirkin
2013-09-02 16:02 ` Marcel Apfelbaum
2013-09-02 15:57 ` Michael S. Tsirkin
2013-09-02 14:30 ` [Qemu-devel] [PATCH RFC 0/3] pci: complete master abort protocol Peter Maydell
2013-09-02 14:39 ` Marcel Apfelbaum
2013-09-02 14:43 ` Peter Maydell
2013-09-02 15:49 ` Marcel Apfelbaum
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=1378136804.2640.36.camel@localhost.localdomain \
--to=marcel.a@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).