All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Henry Wang <Henry.Wang@arm.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Fwd: Ping²: [PATCH] x86: enable interrupts around dump_execstate()
Date: Tue, 19 Jul 2022 12:59:44 +0200	[thread overview]
Message-ID: <3a8d4fe8-de96-06cd-adc7-073bf746d5e2@suse.com> (raw)
In-Reply-To: <3a5a1efc-e610-e151-fa58-25cfd9177f26@suse.com>

Henry,

-------- Forwarded Message --------
Subject: Ping²: [PATCH] x86: enable interrupts around dump_execstate()
Date: Tue, 5 Jul 2022 18:19:38 +0200
From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, Roger Pau Monné <roger.pau@citrix.com>
CC: Wei Liu <wl@xen.org>, xen-devel@lists.xenproject.org <xen-devel@lists.xenproject.org>

>On 11.01.2022 11:08, Jan Beulich wrote:
>> On 16.12.2021 14:33, Jan Beulich wrote:
>>> On 16.12.2021 12:54, Andrew Cooper wrote:
>>>> On 13/12/2021 15:12, Jan Beulich wrote:
>>>>> show_hvm_stack() requires interrupts to be enabled to avoids triggering
>>>>> the consistency check in check_lock() for the p2m lock. To do so in
>>>>> spurious_interrupt() requires adding reentrancy protection / handling
>>>>> there.
>>>>>
>>>>> Fixes: adb715db698b ("x86/HVM: also dump stacks from show_execution_state()")
>>>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> 
>> There's a bug here which we need to deal with one way or another.
>> May I please ask for a response to the issues pointed out with
>> what you said in your earlier reply?
>
>I sincerely hope we won't ship another major version with this
>issue unfixed. The only option beyond applying this patch that I'm
>aware of is to revert the commit pointed at by Fixes:, which imo
>would be a shame (moving us further away from proper PVH support,
>including Dom0).

perhaps another item for the list of things needing resolution for
the release.

Jan


  reply	other threads:[~2022-07-19 11:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 15:12 [PATCH] x86: enable interrupts around dump_execstate() Jan Beulich
2021-12-16 11:54 ` Andrew Cooper
2021-12-16 13:33   ` Jan Beulich
2022-01-11 10:08     ` Ping: " Jan Beulich
2022-07-05 16:19       ` Ping²: " Jan Beulich
2022-07-19 10:59         ` Jan Beulich [this message]
2022-07-19 12:54           ` Henry Wang
2022-07-19 11:22     ` Andrew Cooper
2022-07-19 12:53       ` Jan Beulich
2022-09-13 14:50 ` Roger Pau Monné
2022-09-14  8:14   ` Jan Beulich
2022-09-14  8:31     ` Jan Beulich
2022-09-14  9:13       ` Roger Pau Monné
2022-09-14 10:13         ` Jan Beulich
2022-09-14 14:23           ` Roger Pau Monné
2022-09-15  8:01             ` Jan Beulich
2022-09-15 15:43               ` Roger Pau Monné

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=3a8d4fe8-de96-06cd-adc7-073bf746d5e2@suse.com \
    --to=jbeulich@suse.com \
    --cc=Henry.Wang@arm.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.