All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Debug-Registers in HVM domain destroyed
Date: Thu, 20 Feb 2014 08:07:36 +0000	[thread overview]
Message-ID: <5305C5D8020000780011DEB3@nat28.tlf.novell.com> (raw)
In-Reply-To: <5305B273.9000803@ts.fujitsu.com>

>>> On 20.02.14 at 08:44, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
> On 18.02.2014 13:56, Jan Beulich wrote:
>>>>> On 18.02.14 at 13:48, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
>>> On 14.02.2014 14:02, Jan Beulich wrote:
>>>>>>> On 14.02.14 at 13:18, Juergen Gross <juergen.gross@ts.fujitsu.com> wrote:
>>>>> Is this the case when the guest itself uses single stepping? Initially the
>>>>> debug trap shouldn't cause a VMEXIT, I think.
>>>>
>>>> That looks like a bug, indeed - it's missing from the initially set
>>>> exception_bitmap. Could you check whether adding this in
>>>> construct_vmcs() addresses that part of the issue? (A proper fix
>>>> would likely include further adjustments to the setting of this flag,
>>>> e.g. clearing it alongside clearing the DR intercept.) But then
>>>> again all of this already depends on cpu_has_monitor_trap_flag -
>>>> if that's set on your system, maybe you could try suppressing its
>>>> detection (by removing CPU_BASED_MONITOR_TRAP_FLAG from
>>>> the optional feature set in vmx_init_vmcs_config())?
>>>
>>> I've currently a test running with the attached patch (the bug was hit about
>>> once every 3 hours, test is running now for about 4 hours without problem).
>>> Test machine is running with Xen 4.2.3 hypervisor from SLES11 SP3.
>>
>> Which, if it continues running fine, would confirm the theory.
>> I'd like to defer to the VMX folks though for putting together a
>> proper fix then - I'd likely overlook some corner case.
> 
> Okay, theory confirmed.
> 
> Unless you want to do it, I'll start another thread with the info found so 
> far and include Jun Nakajima and Eddie Dong.

Please do. And perhaps also include Yang Z Zhang.

Jan

      reply	other threads:[~2014-02-20  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  9:33 Debug-Registers in HVM domain destroyed Juergen Gross
2014-02-14 10:40 ` 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 [this message]

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=5305C5D8020000780011DEB3@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=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.