From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Levin <alexander.levin@verizon.com>
Cc: stable@vger.kernel.org, matt@codeblueprint.co.uk
Subject: Re: [PATCH] Revert "KVM: x86: fix missed hardware breakpoints"
Date: Sun, 18 Sep 2016 08:38:09 -0400 (EDT) [thread overview]
Message-ID: <1290443831.307438.1474202289479.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160918004441.GA16340@sasha-lappy>
> > The upshot is that KVM_DEBUGREG_RELOAD is always set when returning
> > from kvm_arch_vcpu_load() in stable, but not in Linus' tree.
> >
> > This happened because [0] and [1] are the same patch. [0] and [1] come
> > from two
> > different merges, and the later merge is trivially resolved; when [2]
> > is applied it reverts both of them. Instead, when using the [1][2][0]
> > order, patches applies normally but "KVM: x86: fix missed hardware
> > breakpoints" is present in the final tree.
> >
> > Cc: stable kernels <stable@vger.kernel.org> # 4.1, 4.4
> > Reported-by: Matt Fleming <matt@codeblueprint.co.uk>
> > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>
> Hey Paolo,
>
> Could you please confirm it's indeed a problem in 4.1? The current 4.1 tree
> seems to be "correct" (the current code doesn't have the line that this
> patch deletes).
Hi Sasha,
yes, 4.1 is good. It's limited to 4.4.
Paolo
next prev parent reply other threads:[~2016-09-18 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 21:52 [PATCH] Revert "KVM: x86: fix missed hardware breakpoints" Paolo Bonzini
[not found] ` <20160918004441.GA16340@sasha-lappy>
2016-09-18 12:38 ` Paolo Bonzini [this message]
2016-09-20 12:10 ` Patch "Revert "KVM: x86: fix missed hardware breakpoints"" has been added to the 4.4-stable tree gregkh
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=1290443831.307438.1474202289479.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexander.levin@verizon.com \
--cc=matt@codeblueprint.co.uk \
--cc=stable@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).