From: Avi Kivity <avi@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH v2] core, x86: Add user return notifiers
Date: Tue, 22 Sep 2009 20:05:42 +0300 [thread overview]
Message-ID: <4AB903E6.6030208@redhat.com> (raw)
In-Reply-To: <1253638554.18939.5.camel@laptop>
On 09/22/2009 07:55 PM, Peter Zijlstra wrote:
>> If you're using lockdep, surely that's not your biggest worry?
>>
> No, but that's all under #ifdef and fully disappears when not enabled.
> Generic return-tu-user notifiers don't sound like they will though.
>
They will if not selected. If selected and not armed, they will have
zero runtime impact since they piggyback on existing branches
(_TIF_DO_NOTIFY_MASK and near relatives). If selected and armed they'll
cause __switch_to_xtra() on every context switch and do_notity_resume()
on syscall exit until disarmed, but then you've asked for it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-09-22 17:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 12:45 [PATCH 0/4] User return notifiers / just-in-time MSR switching for KVM Avi Kivity
2009-09-16 12:45 ` [PATCH 1/4] core, x86: Add user return notifiers Avi Kivity
2009-09-18 18:14 ` H. Peter Anvin
2009-09-19 6:40 ` [PATCH v2] " Avi Kivity
2009-09-22 9:25 ` Avi Kivity
2009-09-22 9:37 ` Arjan van de Ven
2009-09-22 9:48 ` Avi Kivity
2009-09-22 14:32 ` Ingo Molnar
2009-09-22 14:45 ` Avi Kivity
2009-09-22 15:50 ` Avi Kivity
2009-09-22 17:08 ` Avi Kivity
2009-09-22 15:19 ` H. Peter Anvin
2009-10-01 15:21 ` Avi Kivity
2009-10-01 15:25 ` H. Peter Anvin
2009-10-01 15:30 ` Avi Kivity
2009-10-01 18:33 ` H. Peter Anvin
2009-09-22 16:50 ` Peter Zijlstra
2009-09-22 16:52 ` Avi Kivity
2009-09-22 16:55 ` Peter Zijlstra
2009-09-22 17:05 ` Avi Kivity [this message]
2009-09-22 18:06 ` Peter Zijlstra
2009-09-19 6:40 ` [PATCH 1/4] " Avi Kivity
2009-09-16 12:45 ` [PATCH 2/4] KVM: VMX: Move MSR_KERNEL_GS_BASE out of the vmx autoload msr area Avi Kivity
2009-09-16 12:45 ` [PATCH 3/4] KVM: x86 shared msr infrastructure Avi Kivity
2009-09-16 21:21 ` Marcelo Tosatti
2009-09-16 21:24 ` Avi Kivity
2009-09-16 12:45 ` [PATCH 4/4] KVM: VMX: Use " Avi Kivity
2009-10-25 12:23 ` [PATCH 0/4] User return notifiers / just-in-time MSR switching for KVM 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=4AB903E6.6030208@redhat.com \
--to=avi@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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).