From: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>, linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix handling of h_set_dawr
Date: Thu, 20 Jun 2019 11:45:16 +1000 [thread overview]
Message-ID: <1560995116.4771.1.camel@gmail.com> (raw)
In-Reply-To: <87e219c8-1db7-9976-03ce-5a566a8df7ab@kaod.org>
On Mon, 2019-06-17 at 11:06 +0200, Cédric Le Goater wrote:
> On 17/06/2019 09:16, Suraj Jitindar Singh wrote:
> > Series contains 2 patches to fix the host in kernel handling of the
> > hcall
> > h_set_dawr.
> >
> > First patch from Michael Neuling is just a resend added here for
> > clarity.
> >
> > Michael Neuling (1):
> > KVM: PPC: Book3S HV: Fix r3 corruption in h_set_dabr()
> >
> > Suraj Jitindar Singh (1):
> > KVM: PPC: Book3S HV: Only write DAWR[X] when handling h_set_dawr
> > in
> > real mode
>
>
>
> Reviewed-by: Cédric Le Goater <clg@kaod.org>
>
> and
>
> Tested-by: Cédric Le Goater <clg@kaod.org>
>
>
> but I see slowdowns in nested as if the IPIs were not delivered. Have
> we
> touch this part in 5.2 ?
Hi,
I've seen the same and tracked it down to decrementer exceptions not
being delivered when the guest is using large decrementer. I've got a
patch I'm about to send so I'll CC you.
Another option is to disable the large decrementer with:
-machine pseries,cap-large-decr=false
Thanks,
Suraj
>
> Thanks,
>
> C.
>
prev parent reply other threads:[~2019-06-20 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 7:16 [PATCH 0/2] Fix handling of h_set_dawr Suraj Jitindar Singh
2019-06-17 7:16 ` [PATCH 1/2] KVM: PPC: Book3S HV: Fix r3 corruption in h_set_dabr() Suraj Jitindar Singh
2019-06-19 12:36 ` Michael Ellerman
2019-06-17 7:16 ` [PATCH 2/2] KVM: PPC: Book3S HV: Only write DAWR[X] when handling h_set_dawr in real mode Suraj Jitindar Singh
2019-06-17 9:06 ` [PATCH 0/2] Fix handling of h_set_dawr Cédric Le Goater
2019-06-20 1:45 ` Suraj Jitindar Singh [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=1560995116.4771.1.camel@gmail.com \
--to=sjitindarsingh@gmail.com \
--cc=clg@kaod.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
/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).