From: <peng.hao2@zte.com.cn>
To: <mst@redhat.com>
Cc: zhong.weidong@zte.com.cn, ehabkost@redhat.com,
kvm@vger.kernel.org, rkrcmar@redhat.com, qemu-devel@nongnu.org,
liran.alon@oracle.com, pbonzini@redhat.com
Subject: Re: [PATCH V4 4/4] target-i386: add i440fx 0xcf8 portascoalesced_pio
Date: Mon, 27 Aug 2018 23:17:49 +0800 (CST) [thread overview]
Message-ID: <201808272317499067164@zte.com.cn> (raw)
>On Mon, Aug 27, 2018 at 04:25:00PM +0800, peng.hao2@zte.com.cn wrote:
>> >> On 25 Aug 2018, at 15:19, Peng Hao <peng.hao2@zte.com.cn> wrote:
>> >>
>> >> diff --git a/hw/pci-host/piix.c b/hw/pci-host/piix.c
>> >> index 0e60834..da73743 100644
>> >> --- a/hw/pci-host/piix.c
>> >> +++ b/hw/pci-host/piix.c
>> >> @@ -327,6 +327,10 @@ static void i440fx_pcihost_realize(DeviceState *dev, Error **errp)
>> >>
>> >> sysbus_add_io(sbd, 0xcfc, &s->data_mem);
>> >> sysbus_init_ioports(sbd, 0xcfc, 4);
>> >> +
>> >> + /* register i440fx 0xcf8 port as coalesced pio */
>> >> + memory_region_set_flush_coalesced(&s->data_mem);
>> >> + memory_region_add_coalescing(&s->conf_mem, 0, 4);
>> >> }
>> >>
>> >Is there a reason to not register this port as coalesced PIO also for Q35?
>> >In q35_host_realize()?
>> >If not, I would do that as an extra patch as part of this series.
>> Just as I mentioned in patch [0/4] , you can add pci->>host config port as coalesecd pio. I think it works for q35 port 0xcf8.
>> >-Liran
>
>What's the performance improvement for q35?
q35 also has the same pci-host config port 0xcf8 as piix. I test the coalesced pio for
q35 pci-host config port 0xcf8. It spent less VM-exit avg time from 3us to 0.6us.
>--
>MST
next reply other threads:[~2018-08-27 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 15:17 peng.hao2 [this message]
2018-08-31 3:39 ` [PATCH V4 4/4] target-i386: add i440fx 0xcf8 portascoalesced_pio Michael S. Tsirkin
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=201808272317499067164@zte.com.cn \
--to=peng.hao2@zte.com.cn \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=zhong.weidong@zte.com.cn \
/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