All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gleb Natapov <gleb@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>
Subject: Re: [PATCH 0/8] use jump labels to streamline common APIC configuration
Date: Tue, 14 Aug 2012 19:21:10 +0300	[thread overview]
Message-ID: <502A7AF6.7010609@redhat.com> (raw)
In-Reply-To: <502A67AC.3000209@siemens.com>

On 08/14/2012 05:58 PM, Jan Kiszka wrote:
>>>
>>> And regarding how common they are: Do standard OSes trigger any
>>> jump-label optimized switch during at least their boot-up? I thought so.
>>> In that case, if you co-locate RT and standard OSes on a shared host,
>>> you would have a conflict.
>>>
>> Yes, during boot up it happens. But it is rate limited to happen not
>> more than once per second. But I genuinely curious does RT guest have
>> any RT guaranties from QEMU/kvm combination today (with of without
>> jump-labels)?
> 
> Yes, when avoiding userspace exits. If you have a customized RTOS guest
> or are lucky with some existing one, that works pretty well for periodic
> processing in the 1 ms range.

I'd have expected better.

For more formal support, we need some ioctl() to pre-populate mappings,
or perhaps extend mmu notifiers to report mlock un munlock operations
and take them as a hint to premap.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2012-08-14 16:21 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 12:58 [PATCH 0/8] use jump labels to streamline common APIC configuration Gleb Natapov
2012-08-05 12:58 ` [PATCH 1/8] KVM: clean up kvm_(set|get)_apic_base Gleb Natapov
2012-08-05 12:58 ` [PATCH 2/8] KVM: use kvm_lapic_set_base() to change apic_base Gleb Natapov
2012-08-05 12:58 ` [PATCH 3/8] KVM: mark apic enabled on start up Gleb Natapov
2012-08-05 14:14   ` Avi Kivity
2012-08-05 14:17     ` Gleb Natapov
2012-08-05 14:39       ` Avi Kivity
2012-08-05 14:43         ` Gleb Natapov
2012-08-05 12:58 ` [PATCH 4/8] Export jump_label_rate_limit() Gleb Natapov
2012-08-05 14:16   ` Avi Kivity
2012-08-06 12:37     ` Jason Baron
2012-08-05 12:58 ` [PATCH 5/8] KVM: use jump label to optimize checking for HW enabled APIC in APIC_BASE MSR Gleb Natapov
2012-08-05 14:35   ` Avi Kivity
2012-08-05 14:42     ` Gleb Natapov
2012-08-05 14:48       ` Avi Kivity
2012-08-05 14:55         ` Gleb Natapov
2012-08-05 12:58 ` [PATCH 6/8] KVM: use jump label to optimize checking for SW enabled apic in spurious interrupt register Gleb Natapov
2012-08-05 12:58 ` [PATCH 7/8] KVM: use jump label to optimize checking for in kernel local apic presence Gleb Natapov
2012-08-05 12:58 ` [PATCH 8/8] KVM: inline kvm_apic_present() and kvm_lapic_enabled() Gleb Natapov
2012-08-05 13:33 ` [PATCH 0/8] use jump labels to streamline common APIC configuration Avi Kivity
2012-08-05 13:35   ` Gleb Natapov
2012-08-05 13:42     ` Avi Kivity
2012-08-05 13:48       ` Gleb Natapov
2012-08-05 14:00         ` Avi Kivity
2012-08-05 14:03           ` Gleb Natapov
2012-08-14 14:00             ` Jan Kiszka
2012-08-14 14:03               ` Gleb Natapov
2012-08-14 14:20                 ` Jan Kiszka
2012-08-14 14:37                   ` Gleb Natapov
2012-08-14 14:58                     ` Jan Kiszka
2012-08-14 16:21                       ` Avi Kivity [this message]
2012-08-14 16:38                         ` Jan Kiszka
2012-08-14 17:00                           ` Avi Kivity
2012-08-14 17:16                             ` Jan Kiszka
2012-08-14 14:04               ` Avi Kivity
2012-08-14 14:05                 ` Jan Kiszka
2012-08-14 14:08                   ` Gleb Natapov
2012-08-14 14:07                 ` Gleb Natapov
2012-08-14 14:13                   ` Jan Kiszka
2012-08-14 14:44                     ` Gleb Natapov
2012-08-14 15:09                       ` Jan Kiszka
2012-08-05 19:30 ` Eric Northup
2012-08-06  8:35   ` Avi Kivity
2012-08-06  8:52   ` Gleb Natapov
2012-08-06 13:23 ` Avi Kivity

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=502A7AF6.7010609@redhat.com \
    --to=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 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.