qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Matthew Rosato" <mjrosato@linux.ibm.com>,
	"Cornelia Huck" <cohuck@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Pierre Morel <pmorel@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org
Subject: Re: [PATCH for-5.2] s390x/pci: fix endianness issues
Date: Tue, 17 Nov 2020 20:23:50 +0100	[thread overview]
Message-ID: <683c0140-6374-19a5-9208-1b4307404a2f@redhat.com> (raw)
In-Reply-To: <17e3595f-6d12-0dc1-2623-d85163c98d3b@redhat.com>

On 17/11/2020 19.49, Philippe Mathieu-Daudé wrote:
> On 11/17/20 7:39 PM, Thomas Huth wrote:
>> On 17/11/2020 19.30, Philippe Mathieu-Daudé wrote:
>>> On 11/17/20 7:19 PM, Matthew Rosato wrote:
>>>> On 11/17/20 12:59 PM, Philippe Mathieu-Daudé wrote:
>>>>> On 11/17/20 6:13 PM, Cornelia Huck wrote:
>>>>>> zPCI control blocks are big endian, we need to take care that we
>>>>>> do proper accesses in order not to break tcg guests on little endian
>>>>>> hosts.
>>>>>>
>>>>>> Fixes: 28dc86a07299 ("s390x/pci: use a PCI Group structure")
>>>>>> Fixes: 9670ee752727 ("s390x/pci: use a PCI Function structure")
>>>>>> Fixes: 1e7552ff5c34 ("s390x/pci: get zPCI function info from host")
>>>>>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>>>>>> ---
>>>>>>
>>>>>> Works for me with virtio-pci devices for tcg on x86 and s390x, and
>>>>>> for kvm.
>>>>>> The vfio changes are not strictly needed; did not test them due to
>>>>>> lack of
>>>>>> hardware -- testing appreciated. >>
>>>>>> As this fixes a regression, I want this in 5.2.
>>>>>>
>>>>>> ---
>>>>>>   hw/s390x/s390-pci-bus.c  | 12 ++++++------
>>>>>>   hw/s390x/s390-pci-inst.c |  4 ++--
>>>>>>   hw/s390x/s390-pci-vfio.c |  8 ++++----
>>>>>>   3 files changed, 12 insertions(+), 12 deletions(-)
>>>>>>
>>>>>> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
>>>>>> index e0dc20ce4a56..17e64e0b1200 100644
>>>>>> --- a/hw/s390x/s390-pci-bus.c
>>>>>> +++ b/hw/s390x/s390-pci-bus.c
>>>>>> @@ -787,12 +787,12 @@ static void s390_pci_init_default_group(void)
>>>>>>     static void set_pbdev_info(S390PCIBusDevice *pbdev)
>>>>>>   {
>>>>>> -    pbdev->zpci_fn.sdma = ZPCI_SDMA_ADDR;
>>>>>> -    pbdev->zpci_fn.edma = ZPCI_EDMA_ADDR;
>>>>>> -    pbdev->zpci_fn.pchid = 0;
>>>>>> +    stq_p(&pbdev->zpci_fn.sdma, ZPCI_SDMA_ADDR);
>>>>>
>>>>> "zPCI control blocks are big endian" so don't we
>>>>> need the _be_ accessors? stq_be_p() etc...
>>>>>
>>>>
>>>> I don't think this is necessary.  This is only available for target
>>>> s390x, which is always big endian...  cpu-all.h should define stq_p as
>>>> stq_be_p for example inside the #if defined(TARGET_WORDS_BIGENDIAN).
>>>
>>> But if you run on little-endian host, you need to byte-swap that,
>>> isn't it?
>>
>> It's done by the macros. They depend on the target endianess. See cpu-all.h.
> 
> I'm confused because the description is about target endianness,
> but stq_p() is about host alignment.

stq_p() is apparently also about endianess. Why would it depend on
TARGET_WORDS_BIGENDIAN otherwise?

 Thomas



  reply	other threads:[~2020-11-17 19:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 17:13 [PATCH for-5.2] s390x/pci: fix endianness issues Cornelia Huck
2020-11-17 17:59 ` Philippe Mathieu-Daudé
2020-11-17 18:19   ` Matthew Rosato
2020-11-17 18:30     ` Philippe Mathieu-Daudé
2020-11-17 18:39       ` Thomas Huth
2020-11-17 18:49         ` Philippe Mathieu-Daudé
2020-11-17 19:23           ` Thomas Huth [this message]
2020-11-17 19:20 ` Matthew Rosato
2020-11-17 19:21 ` Thomas Huth
2020-11-17 19:49   ` Matthew Rosato
2020-11-18  7:49     ` Cornelia Huck
  -- strict thread matches above, loose matches on Subject: below --
2020-11-18  8:51 Cornelia Huck
2020-11-18  8:53 ` Cornelia Huck
2020-11-18  9:38 ` Thomas Huth
2020-11-18 10:19   ` Cornelia Huck

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=683c0140-6374-19a5-9208-1b4307404a2f@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=philmd@redhat.com \
    --cc=pmorel@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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).