linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>,
	"Jaggi, Manish" <Manish.Jaggi@caviumnetworks.com>
Cc: Josh Cartwright <joshc@ni.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [4.4rt3] Preemption disabled at:[<ffff8000000aba44>] kvm_vcpu_ioctl+0x30c/0x750
Date: Thu, 11 Feb 2016 16:19:55 +0000	[thread overview]
Message-ID: <56BCB4AB.70304@arm.com> (raw)
In-Reply-To: <CAMJs5B_UGDTkT6xA_cKq7DW1P8JOQ-f3O7=UQT+KWTOf1q5MjQ@mail.gmail.com>

On 11/02/16 14:02, Christoffer Dall wrote:
> On Thu, Feb 11, 2016 at 11:46 AM, Jaggi, Manish
> <Manish.Jaggi@caviumnetworks.com> wrote:
>> Thanks Josh.
>> I tried both options
>> a) replace prempt_XXX with migrate_XXX as per the patch
>> b) replacing spin_lock in kvm_vgic_flush_hwstate with raw_spin_lock
>>
>> Host and guest has NO_HZ_FULL=y
>> The cyclictest avg latency / max latency are very high in guest.
>>
>> host: Avg:   28 Max:     180
>> guest: Avg:  168 Max:   19532
>>
>> Running guest within a cset created with -k option
>>
> Our interrupt delivery slowdown is quite high due to the expensive
> world-switch path on KVM/ARM.
> 
> Marc (cc'ed) recently did some optimizations in this area which may be
> worth looking at.

You can have a look at the branch I have on

git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
kvm-arm64/suck-less

though most of it is for GICv2 (and my suspicion is that we're talking
about GICv3 here, given the email addresses...).

Anyway, if there is some specific things that should be looked at to
improve RT in guests with KVM, I'm all ears.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2016-02-11 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  9:33 [4.4rt3] Preemption disabled at:[<ffff8000000aba44>] kvm_vcpu_ioctl+0x30c/0x750 Jaggi, Manish
2016-02-10 16:39 ` Josh Cartwright
2016-02-11 10:46   ` Jaggi, Manish
2016-02-11 14:02     ` Christoffer Dall
2016-02-11 16:19       ` Marc Zyngier [this message]
2016-02-11 15:28     ` Sebastian Andrzej Siewior
2016-02-11 15:31       ` Jaggi, Manish
2016-02-11 14:01   ` Christoffer Dall
2016-02-11 16:10   ` Sebastian Andrzej Siewior
2016-02-11 17:54     ` [PATCH -rt 1/2] genirq: update irq_set_irqchip_state documentation Josh Cartwright
2016-02-11 17:54       ` [PATCH -rt 2/2] KVM: arm/arm64: downgrade preempt_disable()d region to migrate_disable() Josh Cartwright
2016-02-12 23:03         ` Sebastian Andrzej Siewior

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=56BCB4AB.70304@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=Manish.Jaggi@caviumnetworks.com \
    --cc=christoffer.dall@linaro.org \
    --cc=joshc@ni.com \
    --cc=linux-rt-users@vger.kernel.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).