[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] x86/hvm: Fix fast singlestep state persistence


  • To: Petr Beneš <w1benny@xxxxxxxxx>
  • From: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>
  • Date: Fri, 9 Feb 2024 08:53:07 -0500
  • Arc-authentication-results: i=1; mx.zohomail.com; dkim=pass header.i=tklengyel.com; spf=pass smtp.mailfrom=tamas@xxxxxxxxxxxxx; dmarc=pass header.from=<tamas@xxxxxxxxxxxxx>
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1707486823; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=oqnESpiVyk/PjxgNGOrqwPCDLj/GqlaTMXewMMadClQ=; b=PIMDBG9Ilua4/ePvMs7EPx7+6fQckoUYLTJDugsSO6gfMyNKPQN15oN6X50e2OWiLPG/x8kRklCOvehU6ZFAuxIikpz5QoXU9hCf2OZppcRexgKb31AIeQ4k91tvXkddNW6jpetWX1ldwwjb7GiuSGPmKfxjihzfnpore0e9MOA=
  • Arc-seal: i=1; a=rsa-sha256; t=1707486823; cv=none; d=zohomail.com; s=zohoarc; b=mtRQSytfSnfrgPL8u7ZP0DpsqIEqZRXtfJb5z+UAaO0QKy4Ffirhp1RetJVBeJeClcVKNnozZBT+i9htT2SwzAceAbzUSewExNrlETYnvJonKqO2D/VoEwSjep87x8qq6T9eJEmCVf0a4VhbPSTwIOeWi8kfzQmVUyWT8+L0awI=
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>
  • Delivery-date: Fri, 09 Feb 2024 13:54:04 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Thu, Feb 8, 2024 at 4:20 PM Petr Beneš <w1benny@xxxxxxxxx> wrote:
>
> From: Petr Beneš <w1benny@xxxxxxxxx>
>
> This patch addresses an issue where the fast singlestep setting would persist
> despite xc_domain_debug_control being called with 
> XEN_DOMCTL_DEBUG_OP_SINGLE_STEP_OFF.
> Specifically, if fast singlestep was enabled in a VMI session and that session
> stopped before the MTF trap occurred, the fast singlestep setting remained
> active even though MTF itself was disabled.  This led to a situation where, 
> upon
> starting a new VMI session, the first event to trigger an EPT violation would
> cause the corresponding EPT event callback to be skipped due to the lingering
> fast singlestep setting.
>
> The fix ensures that the fast singlestep setting is properly reset when
> disabling single step debugging operations.
>
> Signed-off-by: Petr Beneš <w1benny@xxxxxxxxx>

Thanks, this has been a known bug that awaited a fix for a long time.

Reviewed-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx>



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.