In article ,
Dimitris Karagkasidis wrote:
>On 02/07/2018 11:14 AM, Martin Husemann wrote:
> > QEMU should never let the kernel see any exceptions or other traces of being
> > debugged, IMHO.
> >
> > To me this sounds like a qemu bug.
>
>Martin is right. It is a QEMU bug that only occurs when KVM
On 02/07/2018 11:14 AM, Martin Husemann wrote:
> QEMU should never let the kernel see any exceptions or other traces of being
> debugged, IMHO.
>
> To me this sounds like a qemu bug.
Martin is right. It is a QEMU bug that only occurs when KVM virtualization is
enabled.
I also have a minor cosmet
On 02/07/2018 11:09 AM, Maxime Villard wrote:
> If a T_TRCTRAP exception comes in for no reason, that's a _bug_ in the kernel,
> and it shouldn't be ignored.
Understood.
On 02/07/2018 11:14 AM, Martin Husemann wrote:
> QEMU should never let the kernel see any exceptions or other traces of being
On Wed, Feb 07, 2018 at 11:09:51AM +0100, Maxime Villard wrote:
> When it comes to Qemu's GDB, I'm not sure what would be the correct solution.
> Probably detect the hypervisor (by reading its CPUID leaf if it has one - not
> sure Qemu does), and then behave differently. But the default behavior sh
Le 07/02/2018 à 10:37, Dimitris Karagkasidis a écrit :
Hello,
Currently, the handling of the Trace trap on amd64 and i386 architectures is
problematic under certain conditions. More specifically, on kernels compiled
without DDB and KGDB support, Trace traps within supervisor mode result in
kerne
