From: <peng.hao2@zte.com.cn>
To: <liran.alon@oracle.com>
Cc: zhong.weidong@zte.com.cn, ehabkost@redhat.com,
kvm@vger.kernel.org, rkrcmar@redhat.com, mst@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [PATCH V4 4/4] target-i386: add i440fx 0xcf8portascoalesced_pio
Date: Sat, 1 Sep 2018 18:13:25 +0800 (CST) [thread overview]
Message-ID: <201809011813259071679@zte.com.cn> (raw)
>On Mon, Aug 27, 2018 at 11:17:49PM +0800, peng.hao2@zte.com.cn wrote:
>> >On Mon, Aug 27, 2018 at 04:25:00PM +0800, peng.hao2@zte.com.cn wrote:
>> >> >
>> >> >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.
>so pls include that patch too. piix is mostly feature frozen, piix only
>features aren't likely to be merged.
Hi, Liran，do you want to add the patch about q35 ?
WARNING: multiple messages have this Message-ID (diff)
From: <peng.hao2@zte.com.cn>
To: liran.alon@oracle.com
Cc: pbonzini@redhat.com, ehabkost@redhat.com, rkrcmar@redhat.com,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
zhong.weidong@zte.com.cn, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4 4/4] target-i386: add i440fx 0xcf8portascoalesced_pio
Date: Sat, 1 Sep 2018 18:13:25 +0800 (CST) [thread overview]
Message-ID: <201809011813259071679@zte.com.cn> (raw)
>On Mon, Aug 27, 2018 at 11:17:49PM +0800, peng.hao2@zte.com.cn wrote:
>> >On Mon, Aug 27, 2018 at 04:25:00PM +0800, peng.hao2@zte.com.cn wrote:
>> >> >
>> >> >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.
>so pls include that patch too. piix is mostly feature frozen, piix only
>features aren't likely to be merged.
Hi, Liran，do you want to add the patch about q35 ?
next reply other threads:[~2018-09-01 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 10:13 peng.hao2 [this message]
2018-09-01 10:13 ` [Qemu-devel] [PATCH V4 4/4] target-i386: add i440fx 0xcf8portascoalesced_pio peng.hao2
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=201809011813259071679@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.