All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: State of debug register emulation
Date: Tue, 29 Apr 2008 15:07:25 +0200	[thread overview]
Message-ID: <48171D8D.8090505@siemens.com> (raw)

Hi,

looks like we are getting better and better here in hitting yet
unsupported corner-case features of KVM :). This time our guest fiddles
with hardware debugging registers, but quickly gets unhappy as they do
not yet have the expected effect.

Joerg, I found you SVM-related patch series in the archive which does
not seem to have raised much responses. Is this general direction OK?
Does it allow self-debugging of guests? But how are conflicts resolved
if both guest and host need the physical registers (host debugging the
guest which is debugging itself)?

I would try to dig into the VMX side if the general architecture is
-mostly- clear. [ Sorry, Joerg, someone put the latter type of HW on my
desk :->. Hope I can once check our stuff against SVM as well! ]

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

             reply	other threads:[~2008-04-29 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 13:07 Jan Kiszka [this message]
2008-04-29 14:40 ` State of debug register emulation Joerg Roedel
2008-04-29 16:09   ` Jan Kiszka
2008-04-29 23:10     ` Avi Kivity
2008-05-02  8:47       ` Jan Kiszka
2008-05-02  9:54         ` Avi Kivity

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=48171D8D.8090505@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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.