From: Andy Lutomirski <luto@amacapital.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm list <kvm@vger.kernel.org>, Andy Lutomirski <luto@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rik van Riel <riel@redhat.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/3] context_tracking: remove duplicate enabled check
Date: Tue, 27 Oct 2015 22:19:40 -0700 [thread overview]
Message-ID: <CALCETrU_8-HBQk0Lf0sp6CoP3fNJV90Gd1gpaou-p64KmNB+GA@mail.gmail.com> (raw)
In-Reply-To: <1445996397-32703-2-git-send-email-pbonzini@redhat.com>
On Tue, Oct 27, 2015 at 6:39 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> All calls to context_tracking_enter and context_tracking_exit
> are already checking context_tracking_is_enabled, except the
> context_tracking_user_enter and context_tracking_user_exit
> functions left in for the benefit of assembly calls.
>
> Pull the check up to those functions, by making them simple
> wrappers around the user_enter and user_exit inline functions.
This makes my brain hurt. Assuming that this survives a boot with
CONFIG_CONTEXT_TRACKING_FORCE=y and CONFIG_PROVE_LOCKING=y (with the
implied CONFIG_PROVE_RCU), then:
Acked-by: Andy Lutomirski <luto@kernel.org>
next prev parent reply other threads:[~2015-10-28 5:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 1:39 [PATCH 0/3] context_tracking: streamline code, avoid IRQ save/restore Paolo Bonzini
2015-10-28 1:39 ` [PATCH 1/3] context_tracking: remove duplicate enabled check Paolo Bonzini
2015-10-28 5:19 ` Andy Lutomirski [this message]
2015-11-07 9:38 ` Paolo Bonzini
2015-11-09 13:57 ` Rik van Riel
2015-10-28 1:39 ` [PATCH 2/3] context_tracking: avoid irq_save/irq_restore on guest entry and exit Paolo Bonzini
2015-10-28 5:20 ` Andy Lutomirski
2015-11-09 13:58 ` Rik van Riel
2015-10-28 1:39 ` [PATCH 3/3] x86: context_tracking: avoid irq_save/irq_restore on kernel " Paolo Bonzini
2015-10-28 5:22 ` Andy Lutomirski
2015-10-28 14:51 ` Paolo Bonzini
2016-03-14 19:23 ` Andy Lutomirski
2016-03-15 8:51 ` Paolo Bonzini
2015-10-28 2:05 ` [PATCH 0/3] context_tracking: streamline code, avoid IRQ save/restore Paolo Bonzini
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=CALCETrU_8-HBQk0Lf0sp6CoP3fNJV90Gd1gpaou-p64KmNB+GA@mail.gmail.com \
--to=luto@amacapital.net \
--cc=fweisbec@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=riel@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).