From: Wanpeng Li <kernellwp@gmail.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Wei Huang <wei@redhat.com>
Subject: Re: IPI broadcast latency in the guest is worse when AVIC is enabled
Date: Thu, 13 Aug 2020 15:59:46 +0800 [thread overview]
Message-ID: <CANRm+CweXKPDv0KQOxPA5GQuc0-8FOPKH2dABeUra8AgMWK9yw@mail.gmail.com> (raw)
In-Reply-To: <95c26b17-66c6-0050-053b-faa4d63a2347@redhat.com>
Suravee, any inputs?
On Tue, 11 Aug 2020 at 16:29, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 11/08/20 04:04, Wanpeng Li wrote:
> > We found that the IPI broadcast latency in the guest when AVIC=1,
> > exposing xapic is worse than when AVIC=0, exposing xapic. The host is
> > AMD ROME, 2 sockets, 96 cores, 192 threads, the VM is 180 vCPUs. The
> > guest boots with kvm-hint-dedicated=on, --overcommit cpu-pm=on, -smp
> > 180,sockets=2,cores=45,threads=2, l3-cache=on qemu command-line, the
> > pCPU which vCPU is running on is isolated. Both the guest and host
> > kernel are 5.8 Linus' tree. (Note, if you fails to boot with
> > --overcommit cpu-pm=on, you can comments out commit e72436bc3a52, I
> > have a report here, https://lkml.org/lkml/2020/7/8/308)
> >
> > IPI microbenchmark(https://lkml.org/lkml/2017/12/19/141, Destination
> > Shorthand is All excluding self)
> >
> > avic0_xapic: 12313907508.50 ns
> > avic1_xapic: 19106424733.30 ns
> > avic0_x2apic: 13073988486.00 ns
>
> I think it depends on the microarchitecture implementation of AVIC?
>
> Paolo
>
prev parent reply other threads:[~2020-08-13 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 2:04 IPI broadcast latency in the guest is worse when AVIC is enabled Wanpeng Li
2020-08-11 8:28 ` Paolo Bonzini
2020-08-13 7:59 ` Wanpeng Li [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=CANRm+CweXKPDv0KQOxPA5GQuc0-8FOPKH2dABeUra8AgMWK9yw@mail.gmail.com \
--to=kernellwp@gmail.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wei@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).