From: Fengguang Wu <fengguang.wu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [x86/context_tracking] db23da8b95: inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
Date: Mon, 2 Nov 2015 20:25:47 +0800 [thread overview]
Message-ID: <20151102122547.GA11302@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <563754C8.5060202@redhat.com>
Hi Paolo,
Never mind, it just takes 2 minutes for me. :)
Thanks,
Fengguang
On Mon, Nov 02, 2015 at 01:19:20PM +0100, Paolo Bonzini wrote:
> Hi Fengguang,
>
> this patch is not ready, and is left for 4.5; see Andy's comment at
> http://permalink.gmane.org/gmane.linux.kernel/2072877. Only the other
> two are.
>
> I'm sorry for the inconvenience.
>
> Thanks,
>
> Paolo
>
> On 02/11/2015 13:11, Fengguang Wu wrote:
> > Hi Paolo,
> >
> > FYI, here is another bisect result.
> >
> > https://github.com/0day-ci/linux Paolo-Bonzini/context_tracking-remove-duplicate-enabled-check/20151028-094317
> >
> > commit db23da8b95ece9b57d4cfd63f5ee10502f1af0c8
> > Author: Paolo Bonzini <pbonzini@redhat.com>
> > AuthorDate: Wed Oct 28 02:39:57 2015 +0100
> > Commit: 0day robot <fengguang.wu@intel.com>
> > CommitDate: Wed Oct 28 09:43:20 2015 +0800
> >
> > x86: context_tracking: avoid irq_save/irq_restore on kernel entry and exit
> >
> > x86 always calls user_enter and user_exit with interrupt disabled.
> > Therefore, it is not necessary to check for exceptions, nor to
> > save/restore the IRQ state, when context tracking functions are
> > called by guest_enter and guest_exit.
> >
> > Use the previously introduced __context_tracking_entry and
> > __context_tracking_exit.
> >
> > Cc: Andy Lutomirski <luto@kernel.org>
> > Cc: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Rik van Riel <riel@redhat.com>
> > Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> _______________________________________________
> LKP mailing list
> LKP@lists.01.org
> https://lists.01.org/mailman/listinfo/lkp
prev parent reply other threads:[~2015-11-03 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 4:54 [lkp] [x86] db23da8b95: BUG: using __this_cpu_add_return() in preemptible [00000000] code: init/1 kernel test robot
2015-11-02 12:11 ` [x86/context_tracking] db23da8b95: inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage Fengguang Wu
2015-11-02 12:19 ` Paolo Bonzini
2015-11-02 12:25 ` Fengguang Wu [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=20151102122547.GA11302@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=pbonzini@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
all inboxes | Powered by JetHome®