On Tue, Sep 13, 2016 at 06:58:40PM +0200, Paolo Bonzini wrote:
>
>
> On 13/09/2016 18:57, Greg KH wrote:
> > >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware
> > >> breakpoints")
> > >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware
> > >> breakpoints")
On 13/09/2016 18:57, Greg KH wrote:
> >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware breakpoints")
> >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware breakpoints")
> >> [2] commit 70e4da7a8ff6 ("KVM: x86: fix root cause for missed
> >> hardware breakp
On Tue, Sep 13, 2016 at 06:26:12PM +0200, Paolo Bonzini wrote:
>
>
> On 13/09/2016 16:58, Greg KH wrote:
> > [adding stable@ as this is a stable issue, not a 'normal' issue]
> >
> > On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote:
> >> Folks,
> >>
> >> While hunting down a performan
On 13/09/2016 16:58, Greg KH wrote:
> [adding stable@ as this is a stable issue, not a 'normal' issue]
>
> On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote:
>> Folks,
>>
>> While hunting down a performance issue involving KVM I was surprised
>> to see "native_set_debugreg()" as the f
[adding stable@ as this is a stable issue, not a 'normal' issue]
On Tue, Sep 13, 2016 at 03:51:00PM +0100, Matt Fleming wrote:
> Folks,
>
> While hunting down a performance issue involving KVM I was surprised
> to see "native_set_debugreg()" as the first entry in `perf top`.
>
> Digging deeper,
Folks,
While hunting down a performance issue involving KVM I was surprised
to see "native_set_debugreg()" as the first entry in `perf top`.
Digging deeper, it looks as though the following patches were applied
in the wrong order in -stable. This is the order as they appear in
Linus' tree,
[0]
6 matches
Mail list logo