qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: thuth@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [PATCH] libqos: pci-pc: use 32-bit write for EJ register
Date: Wed, 24 Jun 2020 07:59:22 +0200	[thread overview]
Message-ID: <bb61b6b2-96ce-1f1a-70b3-0bcf25afea09@redhat.com> (raw)
In-Reply-To: <20200623165527-mutt-send-email-mst@kernel.org>

On 23/06/20 22:55, Michael S. Tsirkin wrote:
> On Tue, Jun 23, 2020 at 12:18:51PM -0400, Paolo Bonzini wrote:
>> The memory region ops have min_access_size == 4 so obey it.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> 
> I assume you are queueing this with the memory core change?

Yes, I am.

> 
>> ---
>>  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");
>>  }
>> -- 
>> 2.26.2
> 



  reply	other threads:[~2020-06-24  6:00 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 [this message]
2020-06-24  7:46 ` Thomas Huth
2020-06-24  8:00   ` Paolo Bonzini

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=bb61b6b2-96ce-1f1a-70b3-0bcf25afea09@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).