From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: kraxel@redhat.com, mst@redhat.com
Subject: Re: [PATCH] libqos: pci-pc: use 32-bit write for EJ register
Date: Wed, 24 Jun 2020 10:00:31 +0200 [thread overview]
Message-ID: <1b695e3f-962f-112e-fa3d-11ab3f27caa4@redhat.com> (raw)
In-Reply-To: <63b916b5-cca7-e2fd-5a7b-fe12984eaf45@redhat.com>
On 24/06/20 09:46, Thomas Huth wrote:
> On 23/06/2020 18.18, Paolo Bonzini wrote:
>> The memory region ops have min_access_size == 4 so obey it.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> tests/qtest/libqos/pci-pc.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tests/qtest/libqos/pci-pc.c b/tests/qtest/libqos/pci-pc.c
>> index 0bc591d1da..3bb2eb3ba8 100644
>> --- a/tests/qtest/libqos/pci-pc.c
>> +++ b/tests/qtest/libqos/pci-pc.c
>> @@ -186,7 +186,7 @@ void qpci_unplug_acpi_device_test(QTestState *qts,
>> const char *id, uint8_t slot)
>> g_assert(!qdict_haskey(response, "error"));
>> qobject_unref(response);
>> - qtest_outb(qts, ACPI_PCIHP_ADDR + PCI_EJ_BASE, 1 << slot);
>> + qtest_outl(qts, ACPI_PCIHP_ADDR + PCI_EJ_BASE, 1 << slot);
>> qtest_qmp_eventwait(qts, "DEVICE_DELETED");
>> }
>
> I was a little bit afraid that this could cause endianess issues on big
> endian hosts, but I gave it a try on a s390x machine and it seems to
> work fine.
>
> Tested-by: Thomas Huth <thuth@redhat.com>
Also because this is "pci-pc.c". :)) But seriously: if anything this
would fix big endian bugs, not break them.
Paolo
prev parent reply other threads:[~2020-06-24 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 16:18 [PATCH] libqos: pci-pc: use 32-bit write for EJ register Paolo Bonzini
2020-06-23 20:55 ` Michael S. Tsirkin
2020-06-24 5:59 ` Paolo Bonzini
2020-06-24 7:46 ` Thomas Huth
2020-06-24 8:00 ` Paolo Bonzini [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=1b695e3f-962f-112e-fa3d-11ab3f27caa4@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).