All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: Debug-Registers in HVM domain destroyed
Date: Fri, 14 Feb 2014 10:33:33 +0100	[thread overview]
Message-ID: <52FDE2ED.4030008@ts.fujitsu.com> (raw)

Hi,

we've found a problem with debug registers in HVM domains with Xen (we are
running 4.2, but the code in the hypervisor seems to be unchanged in unstable)
on INTEL processors:

Debug registers are restored on vcpu switch only if db7 has any debug events
activated. This leads to problems in the following cases:

- db0-3 are changed by the guest before events are set "active" in db7. In case
   of a vcpu switch between setting db0-3 and db7, db0-3 are lost. BTW: setting
   db7 before db0-3 is no option, as this could trigger debug interrupts due to
   stale db0-3 contents.

- single stepping is used and vcpu switch occurs between the single step trap
   and reading of db6 in the guest. db6 contents (single step indicator) are
   lost in this case.

Any thoughts?


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PBG PDG ES&S SWE OS6                   Telephone: +49 (0) 89 62060 2932
Fujitsu                                   e-mail: juergen.gross@ts.fujitsu.com
Mies-van-der-Rohe-Str. 8                Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

             reply	other threads:[~2014-02-14  9:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  9:33 Juergen Gross [this message]
2014-02-14 10:40 ` Debug-Registers in HVM domain destroyed Jan Beulich
2014-02-14 12:18   ` Juergen Gross
2014-02-14 13:02     ` Jan Beulich
2014-02-18 12:48       ` Juergen Gross
2014-02-18 12:56         ` Jan Beulich
2014-02-20  7:44           ` Juergen Gross
2014-02-20  8:07             ` Jan Beulich

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=52FDE2ED.4030008@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.