From: Henry Wang <xin.wang2@amd.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
"Juergen Gross" <jgross@suse.com>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Michal Orzel <michal.orzel@amd.com>
Subject: Re: [PATCH] drivers/xen: Improve the late XenStore init protocol
Date: Thu, 16 May 2024 09:25:11 +0800 [thread overview]
Message-ID: <028f29be-0393-4a57-83e2-ea27fe0320d5@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2405151524270.2544314@ubuntu-linux-20-04-desktop>
Hi Stefano,
On 5/16/2024 6:30 AM, Stefano Stabellini wrote:
> On Wed, 15 May 2024, Henry Wang wrote:
>> Currently, the late XenStore init protocol is only triggered properly
>> for the case that HVM_PARAM_STORE_PFN is ~0ULL (invalid). For the
>> case that XenStore interface is allocated but not ready (the connection
>> status is not XENSTORE_CONNECTED), Linux should also wait until the
>> XenStore is set up properly.
>>
>> Introduce a macro to describe the XenStore interface is ready, use
>> it in xenbus_probe_initcall() and xenbus_probe() to select the code
>> path of doing the late XenStore init protocol or not.
>>
>> Take the opportunity to enhance the check of the allocated XenStore
>> interface can be properly mapped, and return error early if the
>> memremap() fails.
>>
>> Signed-off-by: Henry Wang <xin.wang2@amd.com>
>> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
> Please add a Fixes: tag
Sure. Will do.
>> ---
>> drivers/xen/xenbus/xenbus_probe.c | 21 ++++++++++++++++-----
>> 1 file changed, 16 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/xen/xenbus/xenbus_probe.c b/drivers/xen/xenbus/xenbus_probe.c
>> index 3205e5d724c8..8aec0ed1d047 100644
>> --- a/drivers/xen/xenbus/xenbus_probe.c
>> +++ b/drivers/xen/xenbus/xenbus_probe.c
>> @@ -72,6 +72,10 @@ EXPORT_SYMBOL_GPL(xen_store_evtchn);
>> struct xenstore_domain_interface *xen_store_interface;
>> EXPORT_SYMBOL_GPL(xen_store_interface);
>>
>> +#define XS_INTERFACE_READY \
>> + ((xen_store_interface != NULL) && \
>> + (xen_store_interface->connection == XENSTORE_CONNECTED))
>> +
>> enum xenstore_init xen_store_domain_type;
>> EXPORT_SYMBOL_GPL(xen_store_domain_type);
>>
>> @@ -751,9 +755,10 @@ static void xenbus_probe(void)
>> {
>> xenstored_ready = 1;
>>
>> - if (!xen_store_interface) {
>> - xen_store_interface = memremap(xen_store_gfn << XEN_PAGE_SHIFT,
>> - XEN_PAGE_SIZE, MEMREMAP_WB);
>> + if (!xen_store_interface || XS_INTERFACE_READY) {
>> + if (!xen_store_interface)
> These two nested if's don't make sense to me. If XS_INTERFACE_READY
> succeeds, it means that ((xen_store_interface != NULL) &&
> (xen_store_interface->connection == XENSTORE_CONNECTED)).
>
> So it is not possible that xen_store_interface == NULL immediately
> after. Right?
I think this is because we want to free the irq for the late init case,
otherwise the init-dom0less will fail. For the xenstore PFN allocated
case, the connection is already set to CONNECTED when we execute
init-dom0less. But I agree with you, would below diff makes more sense
to you?
diff --git a/drivers/xen/xenbus/xenbus_probe.c
b/drivers/xen/xenbus/xenbus_probe.c
index 8aec0ed1d047..b8005b651a29 100644
--- a/drivers/xen/xenbus/xenbus_probe.c
+++ b/drivers/xen/xenbus/xenbus_probe.c
@@ -76,6 +76,8 @@ EXPORT_SYMBOL_GPL(xen_store_interface);
((xen_store_interface != NULL) && \
(xen_store_interface->connection == XENSTORE_CONNECTED))
+static bool xs_late_init = false;
+
enum xenstore_init xen_store_domain_type;
EXPORT_SYMBOL_GPL(xen_store_domain_type);
@@ -755,7 +757,7 @@ static void xenbus_probe(void)
{
xenstored_ready = 1;
- if (!xen_store_interface || XS_INTERFACE_READY) {
+ if (xs_late_init) {
if (!xen_store_interface)
xen_store_interface = memremap(xen_store_gfn <<
XEN_PAGE_SHIFT,
XEN_PAGE_SIZE, MEMREMAP_WB);
@@ -937,6 +939,8 @@ static irqreturn_t xenbus_late_init(int irq, void
*unused)
int err;
uint64_t v = 0;
+ xs_late_init = true;
+
err = hvm_get_parameter(HVM_PARAM_STORE_PFN, &v);
if (err || !v || !~v)
return IRQ_HANDLED;
>> + xen_store_interface = memremap(xen_store_gfn << XEN_PAGE_SHIFT,
>> + XEN_PAGE_SIZE, MEMREMAP_WB);
>> /*
>> * Now it is safe to free the IRQ used for xenstore late
>> * initialization. No need to unbind: it is about to be
>> @@ -822,7 +827,7 @@ static int __init xenbus_probe_initcall(void)
>> if (xen_store_domain_type == XS_PV ||
>> (xen_store_domain_type == XS_HVM &&
>> !xs_hvm_defer_init_for_callback() &&
>> - xen_store_interface != NULL))
>> + XS_INTERFACE_READY))
>> xenbus_probe();
>>
>> /*
>> @@ -831,7 +836,7 @@ static int __init xenbus_probe_initcall(void)
>> * started, then probe. It will be triggered when communication
>> * starts happening, by waiting on xb_waitq.
>> */
>> - if (xen_store_domain_type == XS_LOCAL || xen_store_interface == NULL) {
>> + if (xen_store_domain_type == XS_LOCAL || !XS_INTERFACE_READY) {
>> struct task_struct *probe_task;
>>
>> probe_task = kthread_run(xenbus_probe_thread, NULL,
>> @@ -1014,6 +1019,12 @@ static int __init xenbus_init(void)
>> xen_store_interface =
>> memremap(xen_store_gfn << XEN_PAGE_SHIFT,
>> XEN_PAGE_SIZE, MEMREMAP_WB);
>> + if (!xen_store_interface) {
>> + pr_err("%s: cannot map HVM_PARAM_STORE_PFN=%llx\n",
>> + __func__, v);
>> + err = -ENOMEM;
> I think this should -EINVAL
Will change.
Kind regards,
Henry
>> + goto out_error;
>> + }
>> if (xen_store_interface->connection != XENSTORE_CONNECTED)
>> wait = true;
>> }
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2024-05-16 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 1:43 Henry Wang
2024-05-15 22:30 ` Stefano Stabellini
2024-05-16 1:25 ` Henry Wang [this message]
2024-05-17 0:52 ` Stefano Stabellini
2024-05-17 1:17 ` Henry Wang
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=028f29be-0393-4a57-83e2-ea27fe0320d5@amd.com \
--to=xin.wang2@amd.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.orzel@amd.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®