All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
	"Jürgen Groß" <jgross@suse.com>,
	x86@kernel.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Paul Durrant <pdurrant@amazon.com>,
	jgrall@amazon.com, karahmed@amazon.de,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] xen: Fix XenStore initialisation for XS_LOCAL
Date: Tue, 26 Jan 2021 16:36:41 -0500	[thread overview]
Message-ID: <da79f47d-de72-1c27-71e4-394b17577682@oracle.com> (raw)
In-Reply-To: <4c9af052a6e0f6485d1de43f2c38b1461996db99.camel@infradead.org>



On 1/26/21 12:01 PM, David Woodhouse wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
> 
> In commit 3499ba8198ca ("xen: Fix event channel callback via INTX/GSI")
> I reworked the triggering of xenbus_probe().
> 
> I tried to simplify things by taking out the workqueue based startup
> triggered from wake_waiting(); the somewhat poorly named xenbus IRQ
> handler.
> 
> I missed the fact that in the XS_LOCAL case (Dom0 starting its own
> xenstored or xenstore-stubdom, which happens after the kernel is booted
> completely), that IRQ-based trigger is still actually needed.
> 
> So... put it back, except more cleanly. By just spawning a xenbus_probe
> thread which waits on xb_waitq and runs the probe the first time it
> gets woken, just as the workqueue-based hack did.
> 
> This is actually a nicer approach for *all* the back ends with different
> interrupt methods, and we can switch them all over to that without the
> complex conditions for when to trigger it. But not in -rc6. This is
> the minimal fix for the regression, although it's a step in the right
> direction instead of doing a partial revert and actually putting the
> workqueue back. It's also simpler than the workqueue.


Wouldn't the minimal fix be to restore wake_waiting() to its previous 

        if (unlikely(xenstored_ready == 0)) {
                xenstored_ready = 1;
                schedule_work(&probe_work);
        }

(And to avoid changing xenbus_probe()'s signature just create a wrapper)

-boris



  reply	other threads:[~2021-01-26 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 13:26 [PATCH v4 0/5] Xen INTX/GSI event channel delivery fixes David Woodhouse
2021-01-13 13:26 ` [PATCH v4 1/5] xen: Fix event channel callback via INTX/GSI David Woodhouse
2021-01-13 13:26 ` [PATCH v4 2/5] xen: Set platform PCI device INTX affinity to CPU0 David Woodhouse
2021-01-13 13:26 ` [PATCH v4 3/5] x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery David Woodhouse
2021-01-13 13:26 ` [PATCH v4 4/5] x86/xen: Don't register Xen IPIs when they aren't going to be used David Woodhouse
2021-01-13 13:26 ` [PATCH v4 5/5] x86/xen: Fix xen_hvm_smp_init() when vector callback not available David Woodhouse
2021-01-13 15:13 ` [PATCH v4 0/5] Xen INTX/GSI event channel delivery fixes Jürgen Groß
2021-01-26 17:01   ` [PATCH] xen: Fix XenStore initialisation for XS_LOCAL David Woodhouse
2021-01-26 21:36     ` Boris Ostrovsky [this message]
2021-01-27  6:57       ` Jürgen Groß
2021-01-27  8:09     ` Jürgen Groß

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=da79f47d-de72-1c27-71e4-394b17577682@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=jgrall@amazon.com \
    --cc=jgross@suse.com \
    --cc=karahmed@amazon.de \
    --cc=pdurrant@amazon.com \
    --cc=sstabellini@kernel.org \
    --cc=x86@kernel.org \
    --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.