From: Marcel Apfelbaum <marcel@redhat.com>
To: Matt Redfearn <matt.redfearn@imgtec.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Yongbok Kim <Yongbok.Kim@imgtec.com>
Subject: Re: [Qemu-devel] [PATCH] PCI: PCIe access should always be little endian
Date: Fri, 29 Sep 2017 15:37:00 +0300 [thread overview]
Message-ID: <4939a30b-6e6d-0634-533f-02630cc5cd3a@redhat.com> (raw)
In-Reply-To: <eda76580-a54a-868d-5b70-d9c6ba75adac@imgtec.com>
On 27/09/2017 11:27, Matt Redfearn wrote:
> ping?
>
Hi Matt,
I think Michael is in PTO, he'll pick up
the patch as soon he is back.
Thanks,
Marcel
>
> On 16/08/17 11:25, Marcel Apfelbaum wrote:
>> On 15/08/2017 17:44, Matt Redfearn wrote:
>>> PCIe busses are always little endian, so set the endianness of the
>>> memory region to little endian rather than native such that operations
>>> work as expected on big endian targets.
>>>
>>> Signed-off-by: Matt Redfearn <matt.redfearn@imgtec.com>
>>
>>
>> Hi Matt,
>> Thanks for the patch.
>>
>>> ---
>>>
>>> hw/pci/pcie_host.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/hw/pci/pcie_host.c b/hw/pci/pcie_host.c
>>> index dcebf57ed45e..553db56778b6 100644
>>> --- a/hw/pci/pcie_host.c
>>> +++ b/hw/pci/pcie_host.c
>>> @@ -81,7 +81,7 @@ static uint64_t pcie_mmcfg_data_read(void *opaque,
>>> static const MemoryRegionOps pcie_mmcfg_ops = {
>>> .read = pcie_mmcfg_data_read,
>>> .write = pcie_mmcfg_data_write,
>>> - .endianness = DEVICE_NATIVE_ENDIAN,
>>> + .endianness = DEVICE_LITTLE_ENDIAN,
>>> };
>>> static void pcie_host_init(Object *obj)
>>>
>>
>>
>> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
>>
>> Thanks,
>> Marcel
>
prev parent reply other threads:[~2017-09-29 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 14:44 [Qemu-devel] [PATCH] PCI: PCIe access should always be little endian Matt Redfearn
2017-08-16 10:25 ` Marcel Apfelbaum
2017-09-27 8:27 ` Matt Redfearn
2017-09-29 12:37 ` Marcel Apfelbaum [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=4939a30b-6e6d-0634-533f-02630cc5cd3a@redhat.com \
--to=marcel@redhat.com \
--cc=Yongbok.Kim@imgtec.com \
--cc=matt.redfearn@imgtec.com \
--cc=mst@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 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).